[Openid-specs-risc] openid/sharedsignals: Comment created on issue 256

[github at oidf.org]

openid/sharedsignals event

Issue Comment created on issue 256
Issue Title: Clarifying the language around the retention of events while a stream is paused
https://github.com/openid/sharedsignals/pull/256

Comment: > > > This just occurred to me - the Transmitter might choose to drop events regardless of the stream status. Should we move this language elsewhere? > > > > > > I'd rather be very specific about when this can happen. AFAIK this can happen when the Receiver doesn't poll frequently enough or the stream is paused. Any other condition? If so, we can just add the same / similar language to the poll delivery section. > > I can think of a number of other cases: > > * Transmitter pushes the event and gets an error code from the Receiver > * Receiver polls frequently but never acks one or more of the SETs > * The event source overwhelms the Transmitter's ability to deliver events (poll or push) > * The Receiver changes the event types requested or the subjects on the stream while an event has not yet been delivered true, so perhaps we can move the language to the Event Delivery section? We should make a new section before the "Push delivery" section, which can talk about conditions under which the Transmitter may drop events
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20250513/9c92199a/attachment.htm>