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

Helge Hess wrote:
> On Wednesday, August 27, 2003, at 02:51 PM, Werner Schuster wrote:
> Maybe I should be more specific why I think that one needs to be careful 
> in choosing the API. The problem with the JOGI API (and the xmlrpcd) is 
> that it always retrieves full OGo document objects which is expensive.

Well, is there a way around that?

> So for example if you just want to display lastname, firstname and email 
> address, you should only query those items from the XML-RPC daemon.

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;
How can I tell the Xml-Rpc Daemon to return only a subset of a document;
eg. if I call person.fetch, how can I limit the resulting documents
 to, say, "Name" and "Nickname"?


> This could either mean introducing something like a "PersonFragment" 
> object (like there are DocumentFragments in DOM) in the JOGI API or just 
> use XML-RPC directly in the "target" API since full document objects are 
> not required anyway.

hm... well, the encapsulationt hat JOGI offers should make that easy;
I mean, if you fetch() an object, you could simply fetch the Id, and if
eg. some "name" field (or whatever) is queried with eg. "getName()",
this would result in a call that fetches only the name;

Anyway, I am getting a bit offtopic for the OO.o Groupware list,
 let's continue on the Xml-Rpc list at OG.o.

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

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