[Patch] Webdav properties in UDSAtoms

[Best, Jan-Pascal van]

> On Fri, 31 May 2002 22:23, Best, Jan-Pascal van wrote:
> > Hundreds, or thousands of appointments? But it may not be so bad,
> > because after the first sync we can maybe check for the 
> "lastmodified"
> > date.
> 
> davOnlyRequestResponsesAfterLastModifiedDate? ;)
> 
> (or something slightly more sane)
> 
> Oh, btw, couldn't you do this lastmodified stuff with DAV_SEARCH?

;) That was the idea.

> > > The only thing to consider now is: when we are not requesting
> > > <allprop/>,
> > > should the additional propfind request be sent as a separate
> > > request? Or
> > > maybe as two <prop> blocks in the same <propfind>, if that works?
> >
> > Sorry,, you lost me there. If we are not requesting <allprop/>,
> > we only request what's in davRequestResponse, so what additional
> > propfind request is there?
> 
> Well, if it doesn't also receive the normal dav items, it 
> won't properly be 
> able to return the correct UDS item to comply with the 
> requirements of the 
> stat.  

I see, ok.

> For now I've just append the required fields onto the 
> davRequestResponse XML provided by the app. 
> The format of the xml provided 
> shoud be that the opening <prop> tag is supplied, in case it 
> needs to define 
> any additional namespaces, but not the closing </prop> (so I 
> can append the 
> other elements we need), sound right?

Sounds a bit awkward, sending incomplete XML elements like that.
But I can't think of a better way.

> One question though... with this XML being in utf8, why are 
> we using a 
> QCString instead of using a QString and calling utf8()?

dfaure answered that.

> (Untested) Patch attached.
Looks good.

Cheers

Jan-Pascal