[MOBY-l] Re: moby-l digest, Vol 1 #71 - 1 msg

[mwilkinson at gene.pbi.nrc.ca]

flipping conversation back to the list...

Alan Robinson wrote:

> > but what struck me was a related scenario where you send a list of
> > objects to a service, and it returns a list of response objects... but
> > there is no way to correlate which input object resulted in which
> > output object!  What an awful oversight...  I see two ways of dealing
> > with this:
>
> I've had this previously with CORBA & SOAP services - I ducked the issue
> by deciding that a client may send only one request at a time, and must
> implement their own iterator & exception catching.

My gut reaction is to avoid ducking the issue in this way...


> As a service provider, this also dealt with other troubling aspects of
> allowing clients to send lists of objects: (i) Do you have to consider
> whether a client sends a list that is too long? e.g. all ID's in GenBank?
> (ii) Does constructing the response object for a large list of input
> objects consume prohibitive amounts of cpu/disk/memory? e.g. BLAST
> reports.

Brian Gilman would say "spit out the answers a bit at a time"...