Hi guys! In my office we've been using the Spring Social project in several of our projects. And we really like it.
But since Twitter changed to the Twitter Rest API 1.1 (TRA) we noticed some unexpected behaviours in the Twitter Spring Social (TSS) library.
We compared the results of queries returned by TSS with the results returned by the requests made with the Apigee tool (a tool for build requests to a lot of services, including Twitter - http://apigee.com/). We found out that the results were inconsistent. In general, the TSS requests are returning less documents.
Investigating the requests built by the TSS we realized that, in the endpoint of the library they are essencially the same. I mean that looking close to the HttpRequest objects we can see that the TSS and the Apigee tool are building the same HTTP request to the Twitter Rest API.
Is there any explanation for this behaviour? Does the TSS filter some results? Maybe this is an issue due to the changes of the TRA 1.1?
I'll apreciate any help here!
Best Regards,
Lucas Saldanha
But since Twitter changed to the Twitter Rest API 1.1 (TRA) we noticed some unexpected behaviours in the Twitter Spring Social (TSS) library.
We compared the results of queries returned by TSS with the results returned by the requests made with the Apigee tool (a tool for build requests to a lot of services, including Twitter - http://apigee.com/). We found out that the results were inconsistent. In general, the TSS requests are returning less documents.
Investigating the requests built by the TSS we realized that, in the endpoint of the library they are essencially the same. I mean that looking close to the HttpRequest objects we can see that the TSS and the Apigee tool are building the same HTTP request to the Twitter Rest API.
Is there any explanation for this behaviour? Does the TSS filter some results? Maybe this is an issue due to the changes of the TRA 1.1?
I'll apreciate any help here!
Best Regards,
Lucas Saldanha