Am Montag, den 20.02.2006, 16:17 +0100 schrieb Malek Hadj-Ali: > i'd like to, say, send back some info to users after a procedure > completed correctly. > > now, i know i can just return some message and deal with it client side, > but i thought it would be convenient to have a standard way to do this.
Actually I consider returning a string as a function result a way of
doing this with a rather low overhead.
> ie if the client receive an xmlrcpc.fault with faultCode=99 instead of 1
> (or an InfoRequest instead of an AbortRequest error class), then it
> knows it's not a "real" error and can display it differently than one
> (not in a dialog but in a status bar for example).
AFAICT, an XMLRPC procedure can only return *either* a function result
*or* a fault code, so we wouldn't win anything in this respect. And for
returning in case of success, I am kinda reluctant to abuse the
exception mechanism for that.
I consider something like
setStatusText (blkFoo.call ("bar", {}))
a clean and straightforward way of getting a string information from the
procedure.
Thanks,
Reinhard
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ Gnue-dev mailing list Gnue-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnue-dev
