[Patch] Webdav properties in UDSAtoms

[Best, Jan-Pascal van]

Hamish Rodda wrote:
> > The main argument against this method is that we now first parse the
> > servers response, then encode the properties as an XML string in the
> > UDSAtom, and then (in the application side) parse the same 
> data again!
> 
> If you ask me this isn't too much to ask of a computer these 
> days, especially 
> where it is only going to be doing so when special features 
> are required anyway.
Not too sure about that: when syncing a calendar to an exchange server,
we might have to do so for every appointment in the store. Which brings 
me to something else: the current webdav stat method seems to send a 
PROPFIND to the server, with no further arguments. Shouldn't it contain
a message body like
  <?xml version="1.0" encoding="utf-8" ?>
     <D:propfind xmlns:D="DAV:">
       <D:allprop/>
     </D:propfind>
as per example 8.1.2 from RFC2518? This would also open the door
for YAM (yet another metadata ;) to instruct HTTPProtocol to 
query for just a selected number of arguments, instead of all 
arguments. The default might even be to query for just the arguments
that are used in davParsePropstats. What do you think?

> I take it you're dropping the idea of removing the 
> restriction to the DAV: 
> namespace from davParsePropstats? 
Yep. The entire reply is sent to the UDS_XML_PROPERTIES
anyway. It's up to the application side to check for namespaces
there.

Cheers, 

Jan-Pascal