Novelty since the last event id
Hi, I know that Tigris supports object notifications which sends you a corresponding web hook. But since Tigris is build on a log, I wonder if it would make sense to expose something where you can consume the Hi, I know that Tigris supports object notifications which sends you a corresponding web hook. But since Tigris is build on a log, I wonder if it would make sense to expose something where you can consume the novelty since the last event id you have polled? Example: your SaaS uses one Tigris bucket with a subfolder per tenant, then you have a job that converts uploaded videos. This job then could remember the event id (logical clock) from the last poll to only check new or changed objects in the bucket.you have polled? Example: your SaaS uses one Tigris bucket with a subfolder per tenant, then you have a job that converts uploaded videos. This job then could remember the event id (logical clock) from the last poll to only check new or changed objects in the bucket.
Claude Code said:
The irony. Their engineering blog on how notifications are built describes precisely the primitive you want: a FoundationDB secondary "change index" ordered by FoundationDB Versionstamp (a logical clock), which an internal background worker polls with a cursor and then fans out to webhooks. So the log-with-cursor exists — it's just not exposed to customers. Your idea (a ListChanges-style API taking a versionstamp cursor) would be a thin layer over what they already run internally. If you want it, I'd file it as a feature request on their community forum — it's a very reasonable ask given the architecture.
Claude Code said:
The irony. Their engineering blog on how notifications are built describes precisely the primitive you want: a FoundationDB secondary "change index" ordered by FoundationDB Versionstamp (a logical clock), which an internal background worker polls with a cursor and then fans out to webhooks. So the log-with-cursor exists — it's just not exposed to customers. Your idea (a ListChanges-style API taking a versionstamp cursor) would be a thin layer over what they already run internally. If you want it, I'd file it as a feature request on their community forum — it's a very reasonable ask given the architecture.
