> > do you means that on server side, i can only free the resource of certion persistent >connection when > > 1. reading/writing error occures when server trys to read/write from the socket; > > 2. server side timeout(can be configed by hand.) occures. > > is there any http headers for keeping the persistent connection, such as: browser >send such messages to the server > every XXX minutes/seconds, just like a heart beat. > > and is there any headers for terminate a persistent connection? > You terminate a connection just by closing it, why do you want another information? The server can close a connection whenevr it wants, even if the client starts sending nasty heartbeat polling requests. This depends on how you program you server to react on DoS attacks, maybe you can use some intelligent IDS. Are you asking the fourth question before the others? (at least) :-) - What service is to be delivered by the application? - To what degree does the application require a connection oriented mode? - What do I have to add to fit within exiting protocols, e.g., http? - What are the basic possibilities of http. Note that even if you would have some additional layer on top of IP+TCP+HTTP+keep-alive-mode, you still have to live with network failures etc. The question is to what degree you want to signal lower level interruption of connectivity to the end user, or whether or not you can or want to keep some session information beyond an interuption. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
