Closed edmar closed 13 years ago
Hi Edmar, In our production environment you can expect that all calls to the reverberations service will be made with a twitter auth token. I expect that the user -> twitter user account mapping will be managed by the gateway as there are several of our services which will need to use this data so it makes sense to hold it centrally. I think this type of request architecture would also work in the scenario that someone wants to take the code away and run it locally as they could ensure that each request to the service contains their auth token. How does that sound? Matt
Matthew, we will need then 2 parameters: secret and key
In the actual version the token used is the same for all requests. This design is not scalable enough for our needs. The API needs to have an api_key that maps to a user token authenticated from twitter.