A generic connection pooling system would make more sense for things like database connections.
When building the classes that you'll expose to SOAP try and forget that HTTP is even involved. HTTP just happens to be the most common carrier of SOAP messages. There's no practical method other than HTTP available today but SOAP isn't supposed to be tied to HTTP by design. It is in fact, but not by design. Get used to that idea and things might start to "flow" more naturally. Just my two cents. Hope it helps. Justin Buist -----Original Message----- From: Joan Pont [mailto:[EMAIL PROTECTED] Sent: Monday, December 01, 2003 1:08 PM To: '[EMAIL PROTECTED]' Subject: RE: Urgent: How to know when a Session has been terminated within Apache SOAP Thanks Scott, Then, there is absolutely no way to free session allocated resources in Apache SOAP? I thought that, for example, releasing a backend database connection when the session-enabled client connection drops would be a very common problem. How do people get around this issue? Do they have to implement some sort of inactivity timers on the backend connections/allocated resources? Thanks! Joan.
