Sami Itkonen wrote:
>
> On Fri, 21 Apr 2000, Patrick Collins wrote:
>
> > Hi all,
> > I'm currently wrapping up a new Perl module that implements a
> > client-side library for the WebDAV protocol (RFC2518).
>
> Great ! I wrote an essay on WebDAV a year ago, noting that there was
> no perl API.. I considered writing a perl module for it, but, alas,
> m'toolazy :)
>
> How complete is the module ? Does it implement all the features in the
> RFC ? What about other features (the ones specified in drafts - yeah,
> I know, there are millions of them) ?
At the moment it implements all of the features except COPY and MOVE.
Not because they're hard, just because I haven't gotten around to it. I
haven't implemented any of the drafts yet like Ordered Collections or
DAV Searching, but I'd love some help :)
As soon as I get it to alpha stage I'll put it up onto webdav.org and
let you all know about it.
> > WebDAV is an extension to HTTP and you can learn about it at
> > http://www.webdav.org. In an nutshell it extends the standard
> > GET,POST,HEAD methods of HTTP/1.1 to include LOCK,UNLOCK,MKCOL,DELETE,
> > and many more...
> >
> > My question is this. Given that DAV is an extension to HTTP, and given
> > that my module requires the LWP modules in order to be installed, it
> > seems a natural place for the module to live in LWP's namespace.
> >
> > Specifically, HTTP::DAV.
>
> I see no problems with this.. like you said, it extends HTTP, thus it
> would seem to be the logical place to put it into.
> --
> Email: [EMAIL PROTECTED], WWW: <URL:http://www.iki.fi/si/>
