data with oauth older than with clientlogin?

[An]

Firstly, thank you for the unofficial docs and this group. It has been
very helpful.

I have been using the clientlogin mechanism and have been fetching
data successfully. I am trying to switch over to oauth and have been
comparing the outputs of both. The data fetched using oauth is always
older (by several hours) than that obtained using clientlogin for the
same account. I am not generating auth tokens everytime, but have been
using reusing the same. The API I am using is /reader/api/0/stream/
contents/

Any help is appreciated.

Thank you.

[Mihai Parparita]

The data should be equivalent (the authentication mechanism does influence what is returned). It is possible that your requests are hitting different datacenters, which may be experiencing replication delay. However, that is usually on the order of minutes, not hours.

Can you send along the full requests and responses for both authentication methods?

Mihai

[Anesh]

Thank you for your reply, Mihai. Much appreciated.

 

I generated new auth keys and it has been working well.

 

Here is what happened (I can’t reproduce it anymore). I generated an auth token(say token1) and was using it. In the meantime I generated another auth token(say token2) while continuing to use token1. The data obtained using token1 was stale. I tried to recreate the same scenario, but have not been able to. Here are screenshots from the time I had the problem.

 

I will respond if I encounter this issue again. Thank you again.

 

 

 

 

Client login

 

 

 

 

Oauth -