|start | find | index | login or register | edit|
by earl, 7026 days ago[as i've not found any explanation of what sandstorm is, on the sstorm pages, the following was copied from a release announcement]
SandStorm is a simple, yet powerful, component system built on top of XML-RPC.
It strongly adheres to the KISS principle(Keep It Simple, Stupid), which XML-RPC is inspired from.
SandStorm provides specification and implementation of an XML-RPC interface allowing components to notify each other location, called the registry.
A component is defined as a set of XML-RPC methods which have a common namespace, for example, if you have these methods:
then hello() and world() are both a component which occupies the namespace "me". the component then registers itself as namespace "me", and his host/port/uri.
A registry aware application can then ask for the component "me", and with a simple wrapper, use the location information to create the correct xml-rpc object, basically allowing to locate component "me" everywhere on the net, with no need to modify the other applications.
SandStorm also defines it's own IDL language, named SIDL. basicly allowing to define interfaces, and then to verify components using the SIDL file and the introspection API.
SandStorm comes with a set of "bindings" for various languages, based on existing XML-RPC bindings. these currently include Java, Python, Ruby, Perl and PHP.
There is a set of "standard" components packed at a seperate distribution, and a sandstorm application, named active-xmlrpc is also available.
SandStorm is designed to be used for distributed applications, specificly web applications.
It allows to divide the various parts of the application to a set of interfaces, which can be implemented easily using any language which supports XML-RPC, with no need to take in account where it will run.
3 active users
|earl.strain.at • esa3 • online for 7266 days • c'est un vanilla site|