On 10 Oct 2008, at 10:26, jstrellner wrote:
Alex: Any easy way to appease everyone who needs to access it, without
doing any infrastructure changes on your part, is to add a new API
call, http://twitter.com/statuses/user_avatar/username (for example).
Then when someone requests that URL, you just do a 302 redirect to the
avatar's current location.
Some of the nice things about doing a 302 temporary redirect are:
- For API Users, they never need to worry about where it is or what it
is named, they just need the twitter username (user id would be good
to support too)
- If you guys ever need to move all of those images out of amazon to
your own, or other solution, you can and it wouldn't effect anyone.
- ability to perform statistical analysis on who is requesting them,
and how often.
- doesn't require any changes to your current caching system, just a
minor change to the API
I like this idea except that doing that is no different to providing
an unlimited API call to get the current avatar URL - it's still
hitting their data retrieval systems just as hard.
-Stut
--
http://stut.net/
