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
xmlrpcpackage 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.
HubClientprivateKey member is now an Object not a String, for greater generality.
HubRunnerclass moved from package
Date: 25 September 2008
Archive: Version 0.2-1
jsamp.xmlrpc.implproperty now correctly propagated to JVM running external hub.
hubmonitorwhich meant that sometimes window did not appear.
Date: 9 December 2008
Archive: Version 0.3
msg-guimode 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.
-xmlrpcflags of command-line tools, and classes
DefaultSendActionManagerwith other, more capable,
SendActionManagersubclasses. 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.GuiHubConnectornow contains the Swing-related functionality which was previously in (its superclass)
client.HubConnector, and also all the functionality from the now removed class
ConnectorGuiAPIs modified to permit use of various different hub implementations (with different graphical characteristics - see
notifyAllhub methods as per agreed modifications to the standard at version 1.1. Affects hub and client API, implementation and test suite.
Date: 27 March 2009
Archive: Version 0.3-1
GuiHubConnector.createRegisterOrHubActionmethod, which registers if it can, else offers the user to start a hub. This may be the only button you need.
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.
SendActionManagerclass. These give another way (button plus combo box) go allow users to trigger a send.
.samplockfile noting that contact XML-RPC URL hostname is configurable.
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.
LogResultHandlerclasses moved from package
Date: 5 August 2009
Archive: Version 1.0
Though this version is numbered 1.0, it's not a giant leap ahead of the previous one (0.3-1). However, this is the first release since SAMP became an IVOA Recommendation, and this toolkit is believed to be fully compliant with that standard. The intention is that backwardly incompatible changes will be kept to a minimum following this release.
jsamp.server.portprovided to allow selection of the default server port.
jsamp.lockfileprovided to support non-standard lockfile location.
samp.secretstring for HubRunner if you don't want it chosen randomly.
Changes to behaviour (note some of these may have backward compatibility issues):
SampUtils.getLocalHost()) is now "127.0.0.1", not the DNS name; in certain network environments this works better than the alternatives, though it's less good for inter-machine communications. This default can be altered by setting the
samp.hostnamesystem property; it has two new special values "[hostname]" and "[hostnumber]".
jsamp.localhost(the old name is still recognised for backward compatibility).
-xmlrpcflag from command-line tools; the
jsamp.xmlrpc.implsystem property should be used instead.
API Changes (note some of these may have backward compatibility issues):
DefaultClientProfileclass; this is now the recommended way of getting a general purpose ClientProfile object (rather than using
StandardClientProfile.getInstance(). Using this will aid pluggability (ability to use with non-standard profiles in the future).
UtilServerclass; this can help to reduce the number of HTTP servers run by a JSAMP application, and provides convenience methods for exporting local (e.g. file: or classpath) URLs.
parseValueutility method to
org.astrogrid.samp.xmlrpc, which is where it should have been.
jsamp.versionfile now included in source zip archive.