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

API compatibility for item ids parameters: ot, nt #7

Closed
cbliu opened this issue Jul 2, 2013 · 4 comments
Closed

API compatibility for item ids parameters: ot, nt #7

cbliu opened this issue Jul 2, 2013 · 4 comments
Labels

Comments

@cbliu
Copy link

cbliu commented Jul 2, 2013

Google Reader API used "ot" parameter only, not "nt". Parameter "ot" in Google Reader API simply means "start time" and is used when "r=o" only. Therefore, "ot" actually means "newer than" which is contrary to your implementation.

Just want to point out this difference for potential API compatibility issue. You might want to make it compatible to Google Reader API or highlight this difference in your API doc.

@evgenynacu
Copy link

Hi!
you are not right. Google Reader had both ot and nt parameters
ot = oldest time (newer than)
nt - newest time (older than)

@krasnoukhov
Copy link
Contributor

Thanks @evgenynacu.
Should them work only for r=o? Could you point me at some doc where it is described?

@krasnoukhov krasnoukhov reopened this Jul 3, 2013
@evgenynacu
Copy link

https://code.google.com/p/google-reader-api/wiki/ApiStreamContents

as I remember, nt doesn't work when you fetch items from oldest to newest
ot - otherwise. (it works only if you do so)

as I know, small number of clients use these parameters so it's up to you implement them or not

Thank you

@krasnoukhov
Copy link
Contributor

Just deployed update, see doc. Thank you!

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

No branches or pull requests

3 participants