On 04/10/2008, at 1:41 AM, Oleg Gusakov wrote:
James,
James William Dumay wrote:
Hey Oleg,
Curious, will the Mecury wagon provider be the new handler for the
dav:
protocol extension?
Yes - Mercury replaces a dav protocol wagon handler if this is the
question.
It does not claim to handle entire DAV protocol, including
versioning, etc. It implements a subset that allows to PUT resources
to the server: see http://www.mail-archive.com/[email protected]/msg77266.html
from Jesse. So Mercury transport handles two-way (PUT and GET)
transactions over http and https.
Yep, it's really just the MKCOL that is important for the standard DAV
servers that by default won't create directories automatically. The
solution Jesse has in place is basically the same as the existing
WebDAV clients, as they don't do any particular locking or other DAV
features either.
- Brett
Thanks,
Oleg
Cheers
James
On Thu, 2008-10-02 at 22:34 -0700, Oleg Gusakov wrote:
I have been testing Mercury wagon provider with 2.2.x and 2.1.x
branches and successfully pass all the ITs but one, please see the
tracking comments in http://jira.codehaus.org/browse/MERCURY-8 and
it's subtasks
The missing test - it0031 - deals with plugin alias remapping,
which happens well above wagon provider. Plus it also fails with
the old providers in place, so I don't think it's an obstacle.
I will stage Mercury wagon tomorrow and post notification on this
list. I think it's ready for 2.1.0-M2 consumption.
Thanks,
Oleg
---------------------------------------------------------------------
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]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
