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]
