Hi Marc, Persistant Connections, or Keep-Alives, are available for both HTTP 1.0 and 1.1 - providing your Web Server supports it.
In HTTP 1.0, the following property is added by the Web server, to the Response Header - if the Browser requests it: ............... Connection: Keep-Alive; ............... In HTTP 1.1, Keep-Alives are assumed so the Header property is not necessary. There are a few "ifs" involved - such as the fact the Browser needs to support Keep-Alives, and the Web-Server does too. If you're overriding the HTTP Response header, then you have to decide to add the Connection: Keep-Alive property dynamically. Although Keep-Alives assist in faster application responses - adding Keep-Alives to "every" connection can cause your whole Server to slow down if it is being heavily used. Just do a www.google.com search on "HTTP Header Keep-alive" for more information. Plus check the documentation of your Web Server. This may also be an ideal time to get a TCP Trace tool, to see if persistant connections are actually working properly, once you implement them. Hope this helps. Cheers....... Scott Cadillac, Witango.org - http://witango.org 403-281-6090 - [EMAIL PROTECTED] -- Information for the Witango Developer Community --------------------- XML-Extranet - http://xml-extra.net 403-281-6090 - [EMAIL PROTECTED] -- Well-formed Development (for hire) --------------------- ----- Original Message ----- From: "marc herman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, March 02, 2003 11:56 AM Subject: Witango-Talk: http header > i am using tango 3.6, webstar 3.0.2, mac os 9.2 > i don't quite understand the configuration and the use of the http > header (contained in the header.htx file) > > the header that we are using specifies: > HTTP/1.0 200 OK<@CRLF>Server: WebSTAR/1.0 ID/ACGI<@CRLF>MIME-Version: > 1.0<@CRLF>Content-Type: > text/html<@CRLF><@SETCOOKIES><@USERREFERENCECOOKIE><@CRLF><@CRLF> > > if i want to take advantage of persistent connections, shouldn't the > http header specify HTTP/1.1? > > where can i find more information on how to configure this header? > > marc herman > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
