Date: 31 July 2008
Archive: version 0.1
Initial release (beta). Targets SAMP WD v1.0 (25 June 2008).
Date: 19 September 2008
Archive: version 0.2
xmlrpc package itself defines a pluggable
interface for providing XML-RPC client and server functionality;
two implementations are also provided, in the packages
xmlrpc.apache
and
xmlrpc.internal.
The Apache one is basically what was there in previous versions;
the internal one is completely freestanding, and if this is used
the Apache XML-RPC library is not required for operation.
snooper:client.HubConnector
to gui.ConnectorGui.HubClient privateKey member is now an Object
not a String, for greater generality.RegInfo(String,String,String) constructor
withdrawn.HubRunner class moved from package hub
to xmlrpc.
Date: 25 September 2008
Archive: Version 0.2-1
jsamp.xmlrpc.impl property now correctly propagated
to JVM running external hub.hubmonitor which meant that
sometimes window did not appear.
Date: 9 December 2008
Archive: Version 0.3
HubRunner in
(default) msg-gui mode and then run
HubTester. Or just use the hub with your own
SAMP clients.
Note that this functionality incurs some overhead - if not used
no such overhead is incurred.
xml-log and rpc-log options
to -xmlrpc flags of command-line tools, and classes
org.astrogrid.samp.xmlrpc.internal.*LoggingInternal*.
DefaultSendActionManager with other,
more capable, SendActionManager subclasses.
This makes it easy to handle the results from messages which
have been sent, for instance by passing the information to the
user graphically or in other ways.
gui.GuiHubConnector now contains the
Swing-related functionality which was previously in
(its superclass) client.HubConnector, and also
all the functionality from the now removed class
gui.ConnectorGui.
HubRunner and ConnectorGui APIs modified
to permit use of various different hub implementations
(with different graphical characteristics -
see HubMode).
-xmlrpc flag.callAll and
notifyAll hub methods as per agreed modifications to
the standard at version 1.1.
Affects hub and client API, implementation and test suite.samp.hub.disconnect
MType.SampUtils.isSampChar() convenience method.createTag method to
HubConnector.string characters.
Date: 27 March 2009
Archive: Version 0.3-1
GuiHubConnector.createRegisterOrHubAction method,
which registers if it can, else offers the user to start a hub.
This may be the only button you need.
call and callAll
to HubConnector - these allow you to make asynchronous
calls so that the results are delivered as callbacks to
supplied objects without having to worry about registering
handlers and matching tags.
createTargetSelector/createTargetAction
methods to SendActionManager class.
These give another way (button plus combo box) go allow users
to trigger a send.
.samp lockfile noting that contact XML-RPC
URL hostname is configurable.
SampUtil.
samp.httpd.
Also added some utility classes in that package to facilitate
serving dynamic resources and resources from the classpath.
This is because having a simple self-contained HTTP server
may be useful for client implementations doing SAMP-like things
other than strictly communicating with the hub.
ResultHandler and LogResultHandler classes
moved from package gui to client.