client-side [was: Re: [Web-SIG] Random thoughts]

[Greg Stein]

Simple answer: to see what a DAV client would look like, see davlib.py.

    http://www.lyra.org/greg/python/

It really *wouldn't* use urllib, which is all about fetching.

On Fri, Oct 31, 2003 at 10:45:04AM -0600, Ian Bicking wrote:
> On Oct 31, 2003, at 10:34 AM, John J Lee wrote:
> >>   * WebDAV
> >
> > I plead ignorance.
> 
> I don't think urllib2 and WebDAV will work very well together, though 
> maybe... in the end, a WebDAV interface has to be a lot more complex 
> than a URL-fetching interface.  So even if WebDAV was built on urllib2, 
> it would end up looking a lot different in the end.
> 
> Though thinking about it... for the most part a WebDAV client could 
> *use* urllib2.  The most important things are just using different 
> methods (PROPFIND, PUT, etc), and setting the body of the request -- 
> these are probably already easy to do with urllib2.  Dealing with 
> multiple error responses, and some of the other error responses that 
> WebDAV defines, may be more challenging urllib2 (or not, I don't know) 
> -- you can do compound operations with WebDAV, and so there may be an 
> error message associated with a specific subrequest.  There's some sort 
> of "multiple response" response code, but the actual responses are in 
> the body of the response.  urllib2 could just do nothing and pass all 
> the information on to the WebDAV client and let it reinterpret the 
> results.
> 
> --
> Ian Bicking | ianb at colorstudy.com | http://blog.ianbicking.org
> 
> 
> _______________________________________________
> Web-SIG mailing list
> Web-SIG at python.org
> Web SIG: http://www.python.org/sigs/web-sig
> Unsubscribe: http://mail.python.org/mailman/options/web-sig/gstein%40lyra.org

-- 
Greg Stein, http://www.lyra.org/