Re: Re: [dev-groupware] Java OpenGroupware API - EarlyAccess Release

Helge Hess wrote:
> > er... OK, I just went through the XML-RPC documentation again, but
> > couldn't find any way to limit the results returned by a fetch or get;
> Try adding the "attributes" key with an array value listing the required 
> attributes.

OK, we'll try that;

> > eg. some "name" field (or whatever) is queried with eg. "getName()",
> > this would result in a call that fetches only the name;
> Which would be highly inefficient as it would result in "attribute-count 
> x records" queries.  You basically need to allow the user to fetch
> "fragments". 

Hmmmm... OK, I guess you mean, if the user wants to have, eg. FirstName, 
LastName and EmailAdress of a Person, that should be queried in one go 
(as a fragment of the whole document) instead of either loading the 
whole Person OR fetching each datum individually (resulting in 3 XmlRpc
function calls);
OK... I see what you mean... hmmmmm... I guess we should give some
thought to opening our XmlRpc Subsystem to the Programmer a little more
instead of completely hiding it; allowing the Programmer to set the
attributes of a fetch() call would be an idea; I suppose, we here, at 
the JOGI HQ, will need to get our thinking caps out again...


> "neat" object model. It can be fixed by "upgrading" fragments to full 
> objects (you might want to study object database technology if you have 
> some sparetime ;-)

Sparetime... yeah... that word that got kicked out of my vocabulary
some time ago... ;-)


> Anyway. My whole point is that there is no "one-API-that-fits-all". JOGI 
> is excellent if you need what it does. It might be wrong if you have 
> specific needs. 

Yup, I see; it's basically like knowing when to use DOM and
when to use SAX when dealing with XML;


murphee
--
Werner Schuster (murphee)
Student of SoftwareEngineering and KnowledgeManagement

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