We wrote a wrapper for WebdavResource for our client applications and each session instanciates an instance of the wrapper and we added methods to test for a connection and reconnect if it has dropped and so forth. As you correctly point out the concurrency issues with trying to share a WebdavResource instance make that untenable. We actually took the commandline client and modeled our wrapper after that with great success, we even have an Axis web service generated from our wrapper class so now we can access slide content via a WSDL web service.
Michael Oliver CTO Alarius Systems LLC 6800 E. Lake Mead Blvd, #1096 Las Vegas, NV 89156 Phone:(702)953-8949 Fax:(702)974-0341 *Note new email changed from [EMAIL PROTECTED] -----Original Message----- From: Richard Sands [mailto:[EMAIL PROTECTED] Sent: Friday, November 11, 2005 5:20 PM To: [email protected] Cc: [EMAIL PROTECTED] Subject: Using WebdavResource I have two Slide user-related questions: 1. Is it better to create one instance of the WebdavResource class and utilize the instance for all file access activities -or- is it better to create one instance of the WebdavResource class for each file access (put/get/proppatch/etc.)? If the former, how is it ensured that timeouts don't occur or the connection goes stale and is terminated? If the latter, how many concurrent WebdavResource connections can exist simultaneously and can this setting be modified? Also, are there a limited number of connections per username? 2. In an initial attempt at creating an API with methods like getFile(), saveFile(), and moveFile() which utilizes Apache Slide client methods, I've ended up with some form of concurrency issues. The settings in slide.properties and Domain.xml seem logical, but I get IOException: Closed Stream Exceptions when getting files with WebdavResource.getMethodData(). Does anybody have a better definition of or explanation for the Closed Stream Exception? Does it close the WebdavResource Connection ensuing the Exception? Might be wrong, but it seems that calling getMethodData() twice on a file might cause problems if for the first time you don't finish reading the stream. --------------------------------------------------------------------- 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]
