[Patch] Webdav properties in UDSAtoms

[Hamish Rodda]

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?

> > 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.  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?

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

(Untested) Patch attached.

Cheers,

Hamish.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kio-http-20020531.patch
Type: text/x-diff
Size: 3314 bytes
Desc: not available
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20020601/adedf195/attachment.patch>