<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.3013.2600" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>I'm resending this because I didn't notice it coming up on the
ml; sorry if it is a duplicate</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2>> I was wondering if it would be possible to implement
WebDAV fully in<BR>> Resources, and not touching anything else. Resources can
munge whatever<BR>> headers they want, etc, and we could just have a base
DAVResource do all<BR>> the XML/Mime encoding.<BR><BR>Yes, my last post
pointed out how that could be done. Though, the stuff I pointed out (eg to make
process able to forward the request content even if the method isn't POST) is
really only what needs to be done.<BR>The only stupid stuff is that the
child-list for the Resources will be duplicated since they need to be a member
of their parent-collection. <BR><BR>So, the DAVResource needs to both represent
resources ("files") and collectionresources. Hm, will it create a new
DAVResource for each step down the tree? And if it hits an exisisting resource,
refer to it? I am not trained in twisted.web =)<BR><BR>Oh, how many times
resource and (dav)resource will confuse<BR><BR>//
phed</FONT></DIV></BODY></HTML>