[MOBY-l] service = method ?

[Mark Wilkinson]

Yabbut...

Realistically, most service providers are not going to want to store 
query results on their servers waiting for the client to get around to 
picking them up.  The simple services are going to just send back the 
originating object as their "bookmark" and say "take this back and give 
it to me again when you are really ready to accept the result".

Maybe this is okay, though... because you gain that intermediate 
opportunity for the service provider to examine what you have given them 
and send you back some metadata if they, for example, know that they are 
going to puke on it... Still, two SOAP calls to do what is effectively a 
single transaction is not very efficient.

Hmmmmmm....

M




Lukas Mueller wrote:
> I like solution (2) a lot. Every moby service would just result in a 
> pointer, that also may hold some metadata about the result-set (if the 
> result set can be generated that fast), for example the length of the 
> response (and we would not need something like a virtualSequence 
> object). For the queries that would take a long time to run, just the 
> pointer would be given, as no metadata will exist at that point. 
> However, methods should exist to query the metadata of the data the 
> pointer points to, once the result becomes available. The client could 
> then decide what part of the result it wants transmitted.
> Cheers
> Lukas
> 

-- 
--------------------------------
"Speed is subsittute fo accurancy."
________________________________

Dr. Mark Wilkinson, RA Bioinformatics
National Research Council, Plant Biotechnology Institute
110 Gymnasium Place, Saskatoon, SK, Canada

phone : (306) 975 5279
pager : (306) 934 2322
mobile: markw_mobile at illuminae dot com