call or reply toward unregistered client
Yohann Granet
yohann.granet at oamp.fr
Thu Feb 12 05:34:05 PST 2009
Hi,
I work with the JSAMP framework (0.3) to implement a package manager in
Java.
During my tests I found out that a "call" or a "reply" toward an
unregistered client throws an Exception
(the class involved is org.astrogrid.samp.xmlrpc.XmlRpcHubConnection)
here, the trace for a "call":
org.astrogrid.samp.client.SampException: -9999:
org.astrogrid.samp.hub.HubServiceException: Client c6 is no longer
registered
at
org.astrogrid.samp.xmlrpc.XmlRpcHubConnection.rawExec(XmlRpcHubConnection.java:187)
at
org.astrogrid.samp.xmlrpc.XmlRpcHubConnection.exec(XmlRpcHubConnection.java:170)
at
org.astrogrid.samp.xmlrpc.XmlRpcHubConnection.call(XmlRpcHubConnection.java:135)
...
and here for a "reply":
org.astrogrid.samp.client.SampException: -9999:
org.astrogrid.samp.hub.HubServiceException: Client c5 is no longer
registered
at
org.astrogrid.samp.xmlrpc.XmlRpcHubConnection.rawExec(XmlRpcHubConnection.java:187)
at
org.astrogrid.samp.xmlrpc.XmlRpcHubConnection.exec(XmlRpcHubConnection.java:170)
at
org.astrogrid.samp.xmlrpc.XmlRpcHubConnection.reply(XmlRpcHubConnection.java:153)
...
I think that an attempt to call (or reply) an absent client shouldn't
cause an Exception launching...
Exceptions are not there to manage particular (but "normal") cases
I think that, instead of an Exception, a "null" returned or a specific
message would be preferable
I don't know how this case is managed by other frameworks...
some ideas or suggestions maybe?
Yohann Granet
More information about the apps-samp
mailing list