Post #2533368
2026-03-26 18:26 UTC
The application-layer can continue processing the message delivered by this operation, now based on your own application logic. Often it'll be something like "move the pawn to field E4", "change the title of the document" or a chat message, or a Text CRDT etc.
Finally we want to acknowledge the operation. This will mark the operation internally as "acked" and next time we subscribe to the same stream we will not receive the message anymore. It's something like a "read receipt".
Replies (1)
-
@p2panda@autonomous.zone 2026-03-26 18:26
By default we're automatically acking messages from the stream for you, since this is a more advanced feature, but why is this important? Imagine your application crashes mid-way or you use it on a mobile phone where it got closed while it was processing something. If we didn't have a chance to ack the message it'll be re-played next time when the app opens again, giving us a chance to make sure we've processed every message at least once.