hi remy,
Following is the piece of code
from the class org.apache.slide.webdav.method.PropFindMethod
revisionDescriptor = content.retrieve(slideToken,
revisionDescriptors);
isCollection = isCollection(revisionDescriptor);
String path = object.getUri();
String absoluteUri = URLDecode(req.getRequestURI());
String relativePath = requestUri;
String toAppend = "";
if (relativePath.length() <= path.length()) {
toAppend = path.substring(relativePath.length());
if ((!absoluteUri.endsWith("/")) &&
(!toAppend.startsWith("/"))) {
toAppend = "/" + toAppend;
}
if (toAppend.equals("/")) {
toAppend = "";
}
}
What is the need for the if condition "relativePath.length() <=
path.length()" .
Under what circumstances does the relative path's length lesser than the
path's length.
Can you please give me an example of when this condition would become true.
rajkumar
-----Original Message-----
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 29, 2001 2:50 PM
To: [EMAIL PROTECTED]
Subject: Re: multiple PUT operations
> Hi,
>
> I tried the scalability of Slide by running PutTestCase and saw that it
> failed on parallel PUT operations with Enlist error for Transactions and I
> wonder if it the case was mentioned before by Remy and Juergen that
parallel
> WRITE impossible because of limited TX support.
It's a limitation at the store level.
> In this case if it is better to make WebdavServlet single threaded until a
> new transaction datastore arrived?
I would say no, because it only concerns a subset of possible operations
(write operations). Read ops are non blocking, but making the servlet single
threaded would also limit read scalability (bad).
It's really only temporary.
Remy
