What should I use instead of HTTP for persistent connections? ----- Original Message ----- From: Dieter Maurer <dieter@handshake.de> Date: Sun, 18 May 2003 23:20:41 +0200 To: "Matt Ficken" <mattficken@mail.com> Subject: Re: [Zope] Keep Alive Connection
Matt Ficken wrote at 2003-5-17 13:12 -0500:
My product needs to send data to the client, and then later send the client more data, over the same connection. HTTP/1.1 created Keep-Alive connections for this reason. I tried setting the response header 'Connection' to 'Keep-Alive', but Zope closes the connection anyway.
It was not for that reason!
HTTP/1.1 allows the server to close a connection at any time.
... Is there a different way I can keep connections alive without locking up Zope or using all the system's CPU cycles?
Do not use HTTP when your application needs persistent connections.
Dieter
-- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup