| 1 |
The Client initiates a bind to the sessionScheduler Object.
-
Given that this is successful, the Client is now ready to invoke the IDL-defined operations defined in the previous slides
|
| 2 |
It starts with the createBahn(String PartyName, String _applicationServerName) throws jdceBahnException function.
-
This would return a true in the event that a new dataBahn Object has been instantiated or
-
a jdceBahnException is raised to signify the prior existence of the desired Bahn.
|
| 3 |
The Client now has the option to decide whether he wishes to join an existing Bahn (party) or initiate the existence of a new one. In the latter case Step[2] is repeated as mentioned earlier.
-
Once the process is over, the Client gets a handle to the dataBahn Object by invoking jdce.byteways.dataBahn getDataBahnHandle(String PartyName, String _applicationServerName) throws jdceBahnException .
|
