aa at astro.ex.ac.uk
Thu Aug 6 07:49:28 PDT 2009
Mark Taylor wrote:
> An obvious use of the bridge would be connecting two hubs on two
> different hosts, used by two different people, so they can share
> data and control of applications. Another possibility would be
> connecting client communities which use incompatible SAMP Profiles.
> You may be able to think of other similar or maybe quite different
> I'm not sure yet whether this is a useful infrastructure component
> or just a toy. I'm interested in other people's opinions on the
> Any further discussion, either privately or on list, is very welcome.
As I've mentioned in the past I use something similar to this,
although probably a bit more single-purpose and not meant for general
use, to bridge the (SAMP/PLASTIC enabled) agents running observing
programmes on my backend server stack with desktop clients to tell the
user about what's going on.
If the user is interested in monitoring the agent in real time they
fire up a SAMP hub and the bridge client, which connects to the SAMP
hub on the server where their agent is running. They then start to
receive SAMP messages from their agent. Some are fairly standard
messages, but I've got a bunch of internal ones to poke and prod
proprietary internal software.
It's not exactly a common use case, but I'd argue that the utility of
this sort of software is certainly present.
More information about the apps-samp