I’m designing a “Twitter Proxy Web Service” for our organization’s various public facing web sites. The purpose of the service is to get around with the rate limit of twitter rest api. Client web sites uses a modified twitter widget to obtain json from my service instead of twitter. My service serves as proxy/caching engine. I would like my service get data from twitter via authenticated request. Since number of client web sites is unknown, I cannot obtain a fixed number of access token in advance from dev.twitter.com. The only feasible oAuth option is xAuth. To that end I have a couple questions:
- Does the access token generated by xAuth allow me to access REST api (same type of GET requests used by twitter widget)? the xAuth doc mentioned Direct message, which I’m not sure about.
- If I perform xAuth multiple times (sending multiple POST requests) with same x_auth_username, does it generate different access tokens? Since rate limit on Rest API is imposed on access token, this is important to me. Ideally I want either every client web site or cached entry in my service using a unique access token.
- If 2. is negative, then does xAuth yield different access token for different x_auth_username?