Ok, well I couldn't figure out what I was doing wrong to keep the server socket open between HTTP requests using the example HTTP code so if anybody is interested, I've implemented a HTTP protocol coder and decoder modeled after the sumup example. It seems to work for simple GET and POST requests, and the keep-alive stuff without any problem.
If anybody wants the code its available but I dont know where to put it. John On 6/30/06, John Preston <[EMAIL PROTECTED]> wrote:
> > I've got the example working fine but I can't see where its calling > > closeSession before each new message, and I've set all the timeouts, > > etc. > > the client is probably closing the connection after it has read all > the data. I'm using a browser to test the server connection. I thought that if I supplied the required headers in the response sent back to the browser (Connection: Keep-Alive, keep-Alive: 300), that it would keep the connection open and the next request from the browser would re-use the connection. Is this not so?. john > -pete > > > -- > [EMAIL PROTECTED] - http://fotap.org/~osi > > > > > >
