Re: Some questions about the API

> I'll try to answer some questions - if something is wrong, please
> correct me! :)

OK, thanks for your answers;


> IIrc you can pass a 'name' argument when creating an account, but it
> won't show up when you fetch the same account again - that should be
> considered as a bug.

Hmm, so when I create an Account, I automatically have a
Person document (which contains no data or empty strings for fields like
 "name"?);


>>  - Enterprise: what fields does this document contain? There is no
>> description of it in the documentation;
> Hrmm, it's not in the docs? Strange - but you can check what fields it
> contains by just fetching some enterprise with XML-RPC - then the fields
> will show up in the reply. I'll have a look at the docs and add the
> missing description.

OK, thats good;
I just rememebered, that there are some other missing documents:
 - JobHistory (they are supposed to be returned by jobs.getHistory);
 - FetchSpecification (well, you explained that below, but it might
be useful to put that in the doc as well);
 - Resource

I don't think these are described anywhere in the doc (at least not
in the "Beschreibung der Dokumente" chapter.


> '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.

yes, that would be useful;


I have another question:
The account.setPassword and account.updatePassword allow to send
an encrypted password as argument; what algorithm is used for the
encryption? Or would it be better to send the passwort unencrypted?
 (as the XML-RPC connection should (in my opinion) be run over
a SSL-secured connection only (at least for serious applications),
sending the password in plaintext should not be a big security problem);


murphee


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