[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
From CAP DELETE...
[EDITORS NOTE: Issues:
- Currently CAP requires that the server return a response status.
However, if there are multiple components deleted, should the UID
also be returned?
Yes!
- VQUERY EXPAND and MAXSIZE parameters do not seem to apply to
deletion?
For DELETE - EXPAND has no meaning...
Some implementors were talking about expanding recurring VEVENTs
as the store them (vs expanding them when queried). So it does
bring up a good point. However, you would be deleting by
date range or UID (all).
Deleting a VEVENT by UID would result in ONE reply as no
matter how the CS stores the VEVENT, there is only ONE VEVENT
with that UID.
Deleting a VEVENT by date/range would be done with a MODIFY
and not a DELETE - you would get one reply.
You DELETE COMPONENTS (or calendars) - not instances of recurrence.
And for MAXSIZE:
Deleting with something like 'all VEVENTs where ATTENDEE contains
user-x' could return N number of replies. So it does sound
like a good idea - as long as the CUA knows that it can not
specify which N are deleted. The CUA would then have to
re-issue the DELETE METHOD - over and over?
** WE NEED A STATEMENT in CAP that says that commands
issued with a MAXSIZE limit MUST BE be repeatedly
called until the end is reached as there is no way
to tell which 'N-number' of components were acted upon.
And that failure to do this probably will result in
undesired effects.
- Can one use DELETE to remove all VALARMs and VTIMEZONEs that
match a certain search criteria and that belong to all components,
event though VALARMs and VTIMEZONEs never exist as independent
components? Or should one use MODIFY? If they can be deleted, do
we return the REQUEST-STATUS of their deletion in a VEVENT or
separately?
VALARMS should have a ALARMID (see my previous post).
VTIMEZONEs have an id.
MODIFY - tricky, as a VALARM and VTIMEZONE have a minimum set
of properties - how could you delete the contents of one of them,
unless you declare that when you do is is the same as DELETE.
So why should we have two ways to do the same thing?
- In the example in CAP where a calendar is deleted all the server
returns is 2.0, nothing else?
I would say the TARGET should be returned also - or PIPELINING
is busted.
- We should not be able to delete any VFREEBUSY components?
I had always assumed that a CS would calculate a VFREEBUSY.
Also a CS VFREEBUSY returned value could be an accumulation
of information stored. So how could you delete that?
On the other hand - if you can store it - you must be
able to delete it?
- Currently one can not delete a VAGENDA and some other component
in the same DELETE command. This seems OK. Anyone see any need
to be able to do this?
I agree.
- Should the MAXRESULTS property of VQUERY apply to deletion? We
can use it to delete only the first n components that match. ]
Then delete by date range if that is what you want. Otherwise there
is no way to know which N instances you deleted. (see above).
-Dougbegin:vcard
n:Royer;Doug
tel;cell:208-520-4044
tel;fax:208-552-1179
tel;work:208-520-4044
x-mozilla-html:TRUE
url:http://Royer.com/People/Doug
org:INET-Consulting LLC
version:2.1
email;internet:Doug@xxxxxxxxx
title:Chief Executive Manager
adr;quoted-printable:;;1795 W. Broadway #266=0D=0A;Idaho Falls;ID;83402;USA
x-mozilla-cpt:;-1
fn:Doug Royer
end:vcard