[Ietf-caldav] resource v collection flagging of scheduling objects

[Mike Douglass]

Another reason for flagging of scheduling objects at the resource level
only...

We should not extend WebDAV in a way that unexpected side effects will
occur when WebDAV operations take place.

So...

if we assume we use flagging of events to mark scheduling objects:

COPY drops the flag - copied scheduling objects become non-scheduling
MOVE retains the flag

then webdav clients introduce the minimum of unexpected side effects -
only deletion will trigger off scheduling operations which might be OK
(unless they do MOVE by COPY+DELETE)

This allows the use of davexplorer for example to move stuff around, or
a simple file browser.


-- 

Mike Douglass                           douglm at rpi.edu
Senior Systems Programmer
Communication & Collaboration Technologies      518 276 6780(voice) 2809
(fax)
Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180