Wednesday, February 22, 2012 | By Manju Rajashekhar (@manju) [09:00 UTC]
Today, we’re open sourcing Twemproxy, a fast, light-weight proxy for the memcached protocol. Twemproxy was primarily developed to reduce open connections to our cache servers. At Twitter, we have thousands of front-end application servers, and we run multiple Unicorn instances on each one. Each instance establishes at least one connection to every cache server.
Wednesday, February 8, 2012 | By Jason Costa (@jasoncosta) [10:01 UTC]
Over the past couple of months, we’ve been able to make it out to some great cities - but we won’t be able to make it to all of them right away. Luckily, a few members from the Twitter developer community have organized Teatime events in their respective cities - and if you’re near one of those cities, we’d love for you to join them. The organizers will give a presentation on the Twitter APIs followed by local companies sharing experiences and best practices for integrating with the platform. Twitter platform team members will be participating remotely during the Q&A session.
Monday, February 6, 2012 | By Arne Rಠ_ಠmann-Kurrik (@kurrik) [15:29 UTC]
As previously announced, we are planning on turning on gzip compression for stream.twitter.com this week. A gzipped stream offers a huge bandwidth reduction over an uncompressed stream, so if you’re consuming streaming data from stream.twitter.com, we encourage you to support this feature.
For information on how to request a compressed stream, and for a workaround to an issue which Java clients may experience, please consult the gzip streams documentation.
Wednesday, February 1, 2012 | By Arne Rಠ_ಠmann-Kurrik (@kurrik) [13:07 UTC]
We’d like to change the content type of error responses to API requests. For anyone unfamiliar with the way things currently work, the current response body for 404, 500, and 503 errors is an HTML-formatted web page, which is a pain point for those of you expecting an XML or JSON response. We want to bring that more in line with the rest of the API, and will be making API error responses match the requested data format where possible.