Hi Luke, I recently dug into the WebdavResource while trying to solve my own problems. I ended up making my own method calls using HttpClient and some of the Webdav methods. Doing it this way, I was able to reuse the same instance of the HttpClient for all of my method calls and only 1 session is created.
Ryan- -----Original Message----- From: luke noel-storr [mailto:[EMAIL PROTECTED] Sent: Monday, May 10, 2004 11:51 AM To: Slide Users Mailing List Subject: Re: Slide Tomcat Sessions - Closing them Hmm, either I misunderstood what you meant, or it doesn't quite fix things the way I expected. I now only construct one webdav resource in my code, however, after running just a few simple getMethods, propFindMethods and reportMethods 5 sessions are created when I expected only one to be created. Any further suggestions? Cheers Luke. ----- Quoting luke noel-storr <[EMAIL PROTECTED]>: > 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] > > -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
