The principal URI should be done by the DAV resource, I think,
because the directory service doesn't get to decide whether we use
those or not.
Same, I think for urn:uuid:GUID, since guids are required for all
records and we should always accept those addresses, rather than
leaving that up to the service.
The directory service should get to extend the address list based
on whatever additional information it can obtain. mailto:EMAIL would
be an example of that.
-wsv
On Feb 15, 2007, at 1:00 PM, Cyrus Daboo wrote:
Hi Wilfredo,
--On February 15, 2007 12:54:47 PM -0800 Wilfredo Sánchez Vega <[EMAIL PROTECTED]
> wrote:
Or it may simply be best to ignore the templates in OD
altogether and
simply populate all of the available address forms.
That would be fine by me, but I would still like to have that done
by the directory service (the parent class) rather than hard-coding
at the point of property lookup.
So we want the server to support for calendar user addresses:
relative principal URI
absolute principal URI (http/https depending on which is running)
email address
urn:uuid
--
Cyrus Daboo
_______________________________________________
calendarserver-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/calendarserver-dev
