chamikara 2005/03/23 14:14:45
Modified: sandesha/xdocs architecture.html Log: added class diagrams to the architecture guide Revision Changes Path 1.3 +38 -26 ws-fx/sandesha/xdocs/architecture.html Index: architecture.html =================================================================== RCS file: /home/cvs/ws-fx/sandesha/xdocs/architecture.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- architecture.html 16 Mar 2005 04:22:45 -0000 1.2 +++ architecture.html 23 Mar 2005 22:14:45 -0000 1.3 @@ -140,10 +140,22 @@ dispatching of the web service request to the actual service. RMInvoker will also put the service response (if any) to the Queue present in the server side.</p> <h3 align="left">Service</h3> -<p > -This is the actual web -service, which will be the Application Destination according to the high-level -architecture.</p> +<p > This is the actual web service, which will be the Application Destination + according to the high-level architecture.</p> +<p > </p> +<h2 >Class diagrams</h2> +<h3 >Sandesha Server</h3> +<p >Following diagram describes the class structure of the Sandesha server.</p> +<p ><img src="images/server_class.png" width="718" height="615"></p> +<h3 >Sandesha Client<br> +</h3> +<p >This diagram describes the class structure of Sandesha Client. </p> +<p><img src="images/client_class.png" width="753" height="388"> </p> +<h3 >Sandesha Queue</h3> +<p >Following describes the sandesha storage classes. Currently we use a temporary + queue to hold messages in memory. We have added the ServerDatabaseDAO class + for adding persistant storage support for Sandesh in the future.</p> +<p ><img src="images/server_queue.png" width="462" height="511"></p> <h2 > Messaging Scenarios</h2> <p > @@ -164,8 +176,8 @@ <p style="text-align:center"> <font size="2">Figure 4: Client Side - Request Only with Synchronous Acknowledgement</font></p> -<p style="text-align:center"> - </p> +<p style="text-align:center"> +</p> <h3 style="text-align: justify;">Client Side - Initialization</h3> <p style="text-align: justify;">This is happening only at the first message of a particular sequence. Web service client should initialize the reliable messaging @@ -176,8 +188,8 @@ <img border="0" src="images/ClientInitialization.png" width="556" height="250"></p> <p style="text-align:center"> <font size="2">Figure 5: Client Side - Initialization</font></p> -<p style="text-align:center"> - </p> +<p style="text-align:center"> +</p> <h3 > Client Side - Termination</h3> <p > @@ -191,8 +203,8 @@ <img border="0" src="images/ClientTermination.png" width="556" height="259"></p> <p style="text-align:center"> <font size="2">Figure 6: Client Side - Termination</font></p> -<p style="text-align:center"> - </p> +<p style="text-align:center"> +</p> <h3 > Client Side - Request Only with Asynchronous Acknowledgement</h3> <p > @@ -205,8 +217,8 @@ <p style="text-align:center"> <font size="2">Figure 7: Client Side - Request Only with Asynchronous Acknowledgement</font></p> -<p style="text-align:center"> - </p> +<p style="text-align:center"> +</p> <h3 > Client Side - Request Response with Synchronous Acknowledgement</h3> <p > @@ -215,15 +227,15 @@ <wsa:From> address. So the sequence acknowledgements will be sent through the same one use for the request (note that; this can only be used with two way transports).</p> -<p > - </p> +<p > +</p> <p style="text-align:center"> <img border="0" src="images/EchoSync.png" width="814" height="403"></p> <p style="text-align:center"> <font size="2">Figure 8: Client Side - Request Response with Synchronous Acknowledgement</font></p> -<p style="text-align:center"> - </p> +<p style="text-align:center"> +</p> <h3 style="text-align:left"> Client Side - Request Response with Asynchronous Acknowledgement</h3> <p style="text-align:left"> @@ -240,8 +252,8 @@ <p style="text-align:center"> <font size="2">Figure 9: Client Side - Request Response with Asynchronous Acknowledgement</font></p> -<p style="text-align:center"> - </p> +<p style="text-align:center"> +</p> <h3 align="left">Server Side - Request Only with Synchronous Acknowledgement</h3> <p align="left">This sequence diagram will illustrate the sequence of operations @@ -254,8 +266,8 @@ <p style="text-align:center"> <font size="2">Figure 10: Server Side - Request Only with Synchronous Acknowledgement</font></p> -<p style="text-align:center"> - </p> +<p style="text-align:center"> +</p> <h3 align="left">Server Side - Request Only with Asynchronous Acknowledgement</h3> <p align="left">This sequence diagram will illustrate the sequence of operations that will be executed when the RMDestination receives a One-way service @@ -278,8 +290,8 @@ <p style="text-align:center"> <font size="2">Figure 11: Server Side - Request Response with Synchronous Acknowledgement</font></p> -<p style="text-align:center"> - </p> +<p style="text-align:center"> +</p> <h3 style="text-align:left"> Server Side - Request Response with Asynchronous Acknowledgement</h3> <p align="left">In this scenario, the RMDestination will receive a service @@ -288,15 +300,15 @@ hence the acknowledgement is sent using the same connection with which the service request has sent while the service response is sent using a different connection.</p> -<p style="text-align:left"> - </p> +<p style="text-align:left"> +</p> <p style="text-align:center"> <img border="0" src="images/ServerWithResponse.png" width="741" height="414"></p> <p style="text-align:center"> <font size="2">Figure 12: Server Side - Request Response with Asynchronous Acknowledgement</font></p> -<p style="text-align:center"> - </p> +<p style="text-align:center"> +</p> <h2 align="left">Conclusions and Future Work</h2> <p align="left">Sandesha implements the WS-ReliableMessaging protocol on top of
