Do you actually have a problem with open sessions or is you interest rather theoretical?
As I explained some time ago, you should use WebdavResource in such a way that you call a WebdavResource constructor only once in your application. This way you have no more than one connection, so you should hit no resource limits, hence my question above. The reason that WebdavResouce.close() does not really close the connection is that this would lead to having to reconnect if a parent or a child obtained by calling listWebdavResources() or getChildResources() issues the next request. You may call this a design deficiency, but this is how you are cuurently supposed to work with the client library. Ingo > Hi, > > I posted a question a few days ago about Slide sessions within Tomcat not being > closed, when using the client Java API. > > I didn't notice any replies so thought I'd post again under a different subject. > > Anyway, if anyone has experiences of trying to close sessions within Tomcat from > within the client API then I'd be glad to hear about it. The .close() method of > a WebdavResource doesn't seem to be working. > > (I'm currently using verion 2.0rc1 on the client side - does the final version > fix this?). > > > Cheers > > Luke. > ----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
