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

Clarify paging mechanism #36

Closed
dmitrizagidulin opened this issue Sep 22, 2016 · 4 comments
Closed

Clarify paging mechanism #36

dmitrizagidulin opened this issue Sep 22, 2016 · 4 comments

Comments

@dmitrizagidulin
Copy link
Contributor

Section 3.4.2 states (emphasis mine):

"A successful GET request on the Inbox [...] MAY be subject to paging or access control restrictions at the receivers discretion"

If consumers may encounter paging, it may be helpful to mention the paging mechanism. Are we talking about LDP Paging? Something Hydra related?

@csarven
Copy link
Member

csarven commented Sep 22, 2016

Point taken. There is not a specific paging model that's overwhelmingly popular. Just to add to the mix, AS2 also offers different paging. We figured that the spec shouldn't enforce this at this point in time (hence "at the receivers discretion").

@csarven
Copy link
Member

csarven commented Sep 22, 2016

Per discussion: https://gitter.im/csarven/ldn?at=57e453a7df21a757301cf4dc moved paging under Considerations.

@dmitrizagidulin
Copy link
Contributor Author

Thanks! That addresses my concern, closing.

@csarven
Copy link
Member

csarven commented Sep 23, 2016

F2F decided that we remove the Considerations section for Paging, and add an inline note along the lines of: This specification does not define a paging mechanism, here are some existing ones..

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

2 participants