[MOBY-l] New GO service at BDGP.

[Paul Gordon]

Hmm.  Thinking from a client programmer's point of view, it would be nice
to be able to systematically distinguish between 

1. A service that returned a blank result
2. A service that does not return a result (e.g. a remote save function)
3. A service that could not execute because I formatted a request
improperly (e.g. server was passed wrong object type)
4. A service that could not execute because something is wrong on the
server.

Perhaps the solution could be 

1. A blank MOBY envelope
2. A special null object?
3. SOAP Client Fault Code
4. SOAP Server Fault Code

----------------------------------------------------
Purgamentum init, exit purgamentum

Paul Gordon
Research Associate
University of Calgary

On Fri, 9 Aug 2002, Mark Wilkinson wrote:

> Simon Twigger wrote:
> 
> > Can I pass a GO ID to this script as well as a keyword?
> 
> if you recode it, yes  ;-)
> 
> > If it does take GO IDs, what would happen if I entered one that was 
> > obsolete?
> 
> generally, MOBY requests that have no "answer" simply return an empty 
> <MOBY> envelope, but this is a decision you must make as the service 
> provider.  It isn't "automated" as such.
> 
> 
> > -------------------------------------------------------------------------------------------------- 
> >
> > Simon Twigger, Ph.D.
> > Assistant Professor, Bioinformatics Research Center
> >
> > Medical College of Wisconsin
> > 8701 Watertown Plank Road,
> > Milwaukee, WI, 53226
> > tel. 414-456-8802, fax 414-456-6595
> >
> > _______________________________________________
> > moby-l mailing list
> > moby-l at biomoby.org
> > http://biomoby.org/mailman/listinfo/moby-l
> >
> 
> 
> _______________________________________________
> moby-l mailing list
> moby-l at biomoby.org
> http://biomoby.org/mailman/listinfo/moby-l
>