Resumable “at least once” pub sub would be exactly the same architectural semantics as a more complete SSE implementation.
A server would keep a buffer of events and a cursor keyed by some kind of event id. Resuming clients would reattach on a new dissociated connection and ask to resume from a particular id.
This is what the id field in events and the last-event-id are for in the SSE specification.
A pub sub system would also not solve the described unidirectional problem.
As inference is so expensive it seems natural to add a sensible stream buffer solution in some middleware and that’s trivial to write. Hell it’s the kind of thing a one paragraph prompt would almost certainly one-shot.
The post seems to be more of a reaction to some specific situation than a meaningful commentary on the protocol or associated architectures.
A server would keep a buffer of events and a cursor keyed by some kind of event id. Resuming clients would reattach on a new dissociated connection and ask to resume from a particular id.
This is what the id field in events and the last-event-id are for in the SSE specification.
A pub sub system would also not solve the described unidirectional problem.
As inference is so expensive it seems natural to add a sensible stream buffer solution in some middleware and that’s trivial to write. Hell it’s the kind of thing a one paragraph prompt would almost certainly one-shot.
The post seems to be more of a reaction to some specific situation than a meaningful commentary on the protocol or associated architectures.