Re: Some questions about the API

>> It's unique for each document in the system.
> Correct: its unique for the whole database. (unique for a document kind
> of makes no sense ;-)

I thought, they might only be unique for a documents of the same type; ie.
while I could have only *one* Person with Id "123", I could also have a
Project with Id "123", etc. But that was answered;


> I still don't find the XML-RPC reference on
>    http://www.opengroupware.org/en/devs/resources/xmlrpc/
> Where did you get it?

er... I am not sure whom you're asking, but if its me: I use the
XML-RPC doc on the SKYRIX website (the link in the OGo developer docs
section under XML-RPC);
The link to the XML-RPC doc on Plone doesn't work;


>> As you found out right, the fetchSpecification for an appointment
>> contains some more attributes like 'startDate', 'endDate', 'resources'
>> 'companies' and 'timeZone'. This confuses a bit, maybe the API and/or
>> the docs need some cleanup in here - the term fetchSpecification is
>> misleading here.
> I cannot follow here. "startDate", "endDate", "resources" and
> "companies" should be regular parts of the qualifier section of the
> fetchspec and "timeZone" should be a hint.

Hmm... well as I understand it, the fetchSpec (for Account, etc.)
has a "qualifier" field which holds a query expression as a string;
whereas the qualifier field for the appointment.fetch argument, is
a map that contains the fields "startDate", ...;


murphee


-- 
OpenGroupware.org XML-RPC
xmlrpc@xxxxxxxxxxxxxxxxx
http://mail.opengroupware.org/mailman/listinfo/xmlrpc