The above was done on separate DELETE commands. The ordering of querys in the SAME command would probably have the same results.
No matter which order they were sent, no matter of they were sent in one or two commands. You can NEVER delete the same UID twice.
However you did not address my cases where it can be shown that the ordering of the querys in the SAME command WILL generate different and conflicting results.
Your cases are generic enough because they deal with pools of entries rather than pools and specific entries. My example of "All events last week" and "VEVENT with UID:12345@QWERTY" is 100% legal and it deals with the case where the 2nd querys delete-vreply WOULD have a UID on it to match it to my QUERYs SELECT information.
For this kind of case we can potentially get mulitple delete-vreplys for the same UID in the _SAME_ command with _different_ REQUEST-STATUSs. So what is the CUA to make of that??
You can NEVER delete the same UID twice no matter how complex the query. It does not say find everything that matches. It says:
"...There MUST BE one "VREPLY" component returned for each object that is deleted or marked for delete. ..."
It does not say that if your query matches the same UID multiple times return the SAME UID multiple times.
Doug Royer | http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@xxxxxxxxx | Office: (208)612-INET
http://Royer.com/People/Doug | Fax: (866)594-8574
| Cell: (208)520-4044Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature