Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for store-and-forward #171

Open
hzbarcea opened this issue Apr 20, 2023 · 2 comments
Open

Support for store-and-forward #171

hzbarcea opened this issue Apr 20, 2023 · 2 comments

Comments

@hzbarcea
Copy link
Member

Is it in the scope of the spec to support a scenario where a notification receiver is temporarily offline, yet the notification sender stores it (with at ttl) and streams then once the notification receiver reestablishes connection?

@csarven
Copy link
Member

csarven commented Apr 20, 2023

I would say handling message failures is an acceptable case without implying that the Notification Protocol needs to define a retry policy.

IIRC, there was some discussion/notes along the lines of continuing messages from where they were left off - need to dig that up.

@TallTed
Copy link
Contributor

TallTed commented Apr 20, 2023

I would certainly hope that the SNP (Solid Notification Protocol) would have robustness similar to SMTP or NNTP. I will also note that SMTP and NNTP routing interruptions of years have occurred, with messages continuing on their way upon restoration of communication (i.e., when the relevant machine(s) were rebooted and/or hubs/switches/routers reconnected), and that even this delayed delivery was appreciated by the recipients/readers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants