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

consumer / receiver difference ? #2

Closed
akuckartz opened this issue Jun 24, 2016 · 2 comments
Closed

consumer / receiver difference ? #2

akuckartz opened this issue Jun 24, 2016 · 2 comments

Comments

@akuckartz
Copy link

Please clarify the difference between consumers and receivers.

@rhiaro
Copy link
Member

rhiaro commented Jun 25, 2016

The receiver is basically the server that has the notifications POSTed to it, whether you think of this like creating resources inside an LDP container, or an endpoint with a script that processes these requests and stores them somewhere. The receiver is also responsible for exposing the POSTed notifications for retreival by other applications.

These other applications are the consumers. They need to know 1. how to discover an Inbox from a resource (such as an article or user profile) and 2. how to fetch the contents of the Inbox, eg. to display it nicely for a human.

They can be implemented completely independently, and we anticipate consumers to be specialised and able to read certain types (vocabularies) of notifications from an Inbox for a particular purpose, not necessarily everything all the time.

Does that help? Is there a specific part of the spec right now where you think this is confusing and could be worded better?

@csarven
Copy link
Member

csarven commented Sep 2, 2016

I think this is sufficiently addressed in the spec at this point. If there is a particular wording that's unclear or can be improved, lets focus on that. Issue #21 also touched on this recently.

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

No branches or pull requests

3 participants