Yeah actually I checked APE project (after this post) and i also found that mr benhutchins also did anew implementation called real time Ajax
Which is (as far as i understand) what APE project is using: The client starts a request (ajax) Then the server loops for at most 30 secs looking for an update. If there is no update the server send a message to refresh the conecction so the client just closes the first ajax as it gets the message but initiates a new Ajax request to the server. If the server had an update then it respons inmidiatly , the client then process the answer and starts a new ajax resquest, so "it is always active" Im not good in english and i dont know why i worte this, so you better read it from the author it self xD http://www.benhutchins.com/project/realtime-ajax On Oct 3, 11:03 am, Fábio M. Costa <[email protected]> wrote: > its because the guys code is a little problematic with big string. > > changing the line 100 & 101: > > response = text.split("<end />"); > response = response[response.length-1]; > > to: > > response = text.substring(text.lastIndexOf('<end />')); > > helps A LOT on this. > > -- > Fábio Miranda Costa > Solucione Sistemas > Engenheiro de interface > > On Sat, Oct 3, 2009 at 12:31 PM, Piotr Zalewa <[email protected]> wrote: > > Just a comment there (benhutchins implementation). > > > <cite>After keeping the same connection open it will easily start using > > massive amounts of CPU for both a server and a web browser.</cite> > > > I tried that and it becomes unusable very quickly. > > > Piotr > > -- > > London, UK
