To add to what Mathew clarified - you will need to send that empty request when server has responded to all your requests. This happens typically when : a) the request was held at CM for the max configured time. b) CM/server had something to send to client.
Regards, Mridul --- On Mon, 11/1/10, Abhinav Singh <[email protected]> wrote: > From: Abhinav Singh <[email protected]> > Subject: Re: [BOSH] Pipelining / avoiding use of 2x HTTP-sockets > To: "Bidirectional Streams Over Synchronous HTTP" <[email protected]> > Date: Monday, 11 January, 2010, 5:38 PM > Will > modify the implementation and see how it goes. > Thanks :D > > Abhinav Singh, > Bangalore, > India > http://abhinavsingh.com > > From: > Matthew Wild <[email protected]> > To: > Bidirectional Streams Over Synchronous HTTP > <[email protected]> > Sent: Mon, > January 11, 2010 5:14:35 PM > Subject: Re: > [BOSH] Pipelining / > avoiding use of 2x HTTP-sockets > > > 2010/1/11 Abhinav Singh <[email protected]>: > > Alright i wrote what i see from my bosh > implementation. Here is the log: > > > > <snip/> > > > > > Now from the discussion i assume, my client side js > should not be send an > > extra request after an empty response returned for > previous holded request. > > It should ideally wait for the response of sendMessage > request which ideally > > will be holded by the server until new data is > available, right? > > > > It's hard to tell when the requests aren't linked > with the responses > in your log. But it does look that way, yes - the last new > request > isn't necessary because the one that sent > "Hi" is already open, and > can be held by the server. > > Matthew > > > > > > > > The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/
