Re: [Fwd: Re: CAP-12-a: Stored queries still?]
| Newsgroups | gmane.ietf.calendar |
|---|---|
| Message-ID | <OFE15571CB.5E227010-ON85256D97.004FA3EB-85256D97.0052EA83@notesdev.ibm.com> |
Tim wrote on 09/03/2003 11:12:42 PM: > I agree with Doug that > there are queries which can be stored without need for wild cards, but I'm > not sure I see where the efficiency comes in. I think we all agree that not all stored querys need to use wildcards. If we consider the original intent of the feature, the current design misses the mark and the efficiency for other cases is somewhat tenuous. > Is it intended that the > stored queries be on the Calendar Store machine, such that a > smaller-footprint client can invoke them just by name, like a remote > procedure call of some sort? The original intent was to provide a means for clients to save on space and cycles by not having to recraft commonly used queries and resend them. Queries like "What alarms trigger in the next 10 minutes?" or "Is there anything new for me to look at" or "What entries are on my calendar for this morning/today?", etc. Its possible to craft and store uncommon or infrequently used queries and save them away either locally or on the CS. However making every CS support this feature that does not fulfill the original intent is something I have a concern about. CAP implcitly mandates every CS support stored queries: there is nothing in CAP about how a CS can not support stored queries or how a CUA detects this. This is another mistake that CAP needs to correct. However being a proponent of KISS, I think the better solution is to remove the feature from CAP 1.0 altogether since it fails to meets it original intent and creates an implicit onus on CS's that is not clear no optional. Bruce =========================================================================== Bruce Kahn INet: [email protected] Messaging & Collaboration Phone: 978.399.6496 IBM Software Group FAX: and nothing but the FAX... Standard disclaimers apply, even where prohibited by law...