Mailing-List: contact dev-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@archiva.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-Id: <6FC09B46-BC1A-40E1-BFC2-DEDEEF957290@atlassian.com>
From: James William Dumay <james@atlassian.com>
To: dev@archiva.apache.org
In-Reply-To: <CF4DAA2C-2900-410C-A668-4AC6B63BF316@apache.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Remove support for webdav?
Date: Thu, 26 Feb 2009 17:38:33 +1100
References: <1234312590.3287.21.camel@heck>
 <1a57a2980902121846p2df21b7eh812c0fbfd529dc3f@mail.gmail.com>
 <CF4DAA2C-2900-410C-A668-4AC6B63BF316@apache.org>


Hey Brett,
On 26/02/2009, at 5:32 PM, Brett Porter wrote:

> I agree with Deng.
>
> I thought WebDAV was a reasonable choice for the central web  
> interface since it forced it to be resource-based and gave a bit of  
> extra functionality. I know that we still had it a little tangled up  
> though.
>
> I've no objection to abstracting it a layer away, but if it's at all  
> hard to add Jackrabbit on top of what remains (plugin? :) then I'd  
> think something has gone horribly wrong. We've (ok, you've!) already  
> done most of the hard work of figuring out some of the client and  
> locking issues - if we don't have a direct need for that then we can  
> document that it is only partially supported and let people that  
> want to fix that do so themselves, right?

Its not difficult to add webdav functionality back in. At this point  
I'd probably not recommend going the jackrabbit way again - the  
net.sf.webdav-servlet dudes have done a really excellent job on  
implementing a new servlet that is not quite so tied up in the  
jackrabbit way of doing things.

Cheers
James