Begin main content
Search · Index
No registered users in community xorb-doc
in last 10 minutes


Glueing to ...? A Quickstart

Say, you want to realise a scenario as depicted in Figure 1, i.e. you want to use the simple echo functionality provided by a remote object or remote procedure. In this example scenario, we want to issue a virtual call 'echoFloat' that requires a single argument of type 'float ' (as defined as 'built-in' simple type by the XML schema specification ) as input and promises to return a value of the very same type.

Consumer/client scenario

You just need three little steps to get there:

namespace import ::xosoap::client::*

First, set the stage by import the appropriate facilities into your current namespace. Note, this is not strictly required, it is rather recommended for the sake of convenience. Take a look at the section dedicated to the actual locality of your consumer or client declaration, there might be additional 'staging' requirements depending on where you drop your code!
set glue [SoapGlueObject new \ 
	-endpoint http://websrv.cs.fsu.edu/~engelen/interop2.cgi \ 
	-callNamespace http://soapinterop.org/]
In order to call  a remote object (OO-RPC) or a remote  procedure (RPC), two steps are involved. First, we need a local representation of the remote interface, commonly referred to a 'Client Proxy'. Second, we need to provide configuration information that helps to carry the virtual call to a remote object or remote procedure through all stages involved, especially marshaling and transport. The second step is, in the realm of xorb, referred to as the provision of at least one or several 'Context Objects'. 'Context objects', a term to be found in literature, are called 'glue objects' in xorb and its protocol plug-ins.

Client proxies and context objects

Getting glued to ...? Another Quickstart
Provider/server scenario
How to provide functionalities through remoting ...