Hi, I don't have a problem in terms of errors or crashes or anything; however, I was in fear of the rapidly increasing session count (into several thousands after just a few calls to a servlet I had).
I shall now recode based on your advice though - thank you for your help. Cheers Luke. ----- Quoting Ingo Brunberg <[EMAIL PROTECTED]>: > 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
