Yeah, I was just wondering though if all the overhead of setting up and tearing down connections for each request makes sense when a client might need to download hundreds of statuses (to be stored in local cache) the first time someone uses it.
On Apr 9, 3:34 pm, Chad Etzel <jazzyc...@gmail.com> wrote: > I would guess that when you have millions of connection requests a day > coming into a few different servers, you don't want the connection to > stay open for any longer than it needs to be. Get in, serve data, get > out. > -Chad > > On Thu, Apr 9, 2009 at 2:02 PM, orange80 <jpsw...@gmail.com> wrote: > > > Any reason why not? Just curious. Nice API by the way :) > > > Thanks, > > Jamie > > > On Apr 9, 12:47 am, John Adams <j...@twitter.com> wrote: > >> On Apr 8, 2009, at 10:33 PM, orange80 wrote: > > >> > Yeah, I started checking the headers and realized that. It doesn't > >> > seem like there's any hard limit on simultaneous connections though so > >> > that helps quite a bit. > > >> Our web servers do not support Keep-Alive. > > >> -j > > >> --- > >> John Adams > >> Twitter Operations > >> j...@twitter.comhttp://twitter.com/netik
