Can check this next week maybe. A proxy has it's own connection that can be keep-alive. There should be no problem though, it's been tested with V3 even thru SSL proxy's like the bluecoat proxy which does SSL filtering
Paul ----- Original Message ----- From: "Francois PIETTE" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Sunday, May 13, 2007 6:48 PM Subject: Re: [twsocket] HttpServ fixed > Looking at all use of FKeepAlive, I think it is better to always set > FKeepAlive to false where it is assigned. This will add the header lines > accordingly in the answer. looks more consistent to me. > > btw: Shouldn't you act on the client side in your application and set > keep-alive to 'close' (property THttpCli.Connection set to 'close') ? This > would have the same effect without making a special case in server code > for > your application. Properly handling keep-alives would probably help when > using proxy and similar devices. > > -- > [EMAIL PROTECTED] > The author for the freeware multi-tier middleware MidWare > The author of the freeware Internet Component Suite (ICS) > http://www.overbyte.be > > > ----- Original Message ----- > From: "Paul" <[EMAIL PROTECTED]> > To: "ICS support mailing" <twsocket@elists.org> > Sent: Sunday, May 13, 2007 6:36 PM > Subject: Re: [twsocket] HttpServ fixed > > >> Changed them all >>> Why not act where FKeepAlive is assigned instead instead of where it is >>> used >> Wasn't sure that would work different in other places. >> I can't test the service locally and the downtime of those servers have >> to >> be an abolute minimum >> >> Paul >> >> ----- Original Message ----- >> From: "Francois PIETTE" <[EMAIL PROTECTED]> >> To: "ICS support mailing" <twsocket@elists.org> >> Sent: Sunday, May 13, 2007 5:38 PM >> Subject: Re: [twsocket] HttpServ fixed >> >> >>>> {$IFNDEF NO_KEEPALIVE_CLOSE_CHECK} >>>> if FKeepAlive = FALSE then {Bjornar} >>>> {$ENDIF} >>>> CloseDelayed; >>> >>> There are a lot of places where " if FKeepAlive = FALSE then {Bjornar}" >>> code is. Do have changed all ? >>> Why not act where FKeepAlive is assigned instead instead of where it is >>> used >>> ? >>> >>> -- >>> [EMAIL PROTECTED] >>> The author for the freeware multi-tier middleware MidWare >>> The author of the freeware Internet Component Suite (ICS) >>> http://www.overbyte.be >>> >>> >>> ----- Original Message ----- >>> From: "Paul" <[EMAIL PROTECTED]> >>> To: "TWsocket" <twsocket@elists.org> >>> Sent: Sunday, May 13, 2007 4:14 PM >>> Subject: [twsocket] HttpServ fixed >>> >>> >>>> Fixed the problem I had with one server compiled with V5h >>>> >>>> Bjornar added this line at several places : >>>> if FKeepAlive = FALSE then {Bjornar} <-- added >>>> CloseDelayed; >>>> >>>> This particular server needs to answer other clients directly within >>>> the >>>> OnGetDocument event of another client. >>>> I added a new compiler directive for my personal use and all works fine >>>> now. >>>> >>>> {$IFNDEF NO_KEEPALIVE_CLOSE_CHECK} >>>> if FKeepAlive = FALSE then {Bjornar} >>>> {$ENDIF} >>>> CloseDelayed; >>>> >>>> Paul >>>> >>>> -- >>>> To unsubscribe or change your settings for TWSocket mailing list >>>> please goto http://www.elists.org/mailman/listinfo/twsocket >>>> Visit our website at http://www.overbyte.be >>> >>> -- >>> To unsubscribe or change your settings for TWSocket mailing list >>> please goto http://www.elists.org/mailman/listinfo/twsocket >>> Visit our website at http://www.overbyte.be >>> >>> >> >> -- >> To unsubscribe or change your settings for TWSocket mailing list >> please goto http://www.elists.org/mailman/listinfo/twsocket >> Visit our website at http://www.overbyte.be > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be > > -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be