2
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
3
<title>Chapter 13. Client programming model</title><link rel="stylesheet" href="css/html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.65.1"><link rel="home" href="index.html" title="JBoss Remoting Guide"><link rel="up" href="index.html" title="JBoss Remoting Guide"><link rel="previous" href="ch12.html" title="Chapter 12. How to use it - sample code"><link rel="next" href="ch14.html" title="Chapter 14. Compatibility and versioning"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 13. Client programming model</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch12.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch14.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d0e8253"></a>Chapter 13. Client programming model</h2></div></div><div></div></div><p>The approach taken for the programming model on the client side is
4
one based on a session based model. This means that it is expected that
5
once a Client is created for a particular target server, it will be used
6
exclusively to make calls on that server. This expectation dictates some
7
of the behavior of the remoting client.</p><p>For example, if create a Client on the client side to make server
8
invocations, including adding callback listeners, will have to use that
9
same instance of Client to remove the callback listeners. This is because
10
the Client creates a unique session id that it passes within the calls to
11
the server. This id is used as part of the key for registering callback
12
listeners on the server. If create a new Client instance and attempt to
13
remove the callback listeners, a new session id will be passed to the
14
server invoker, who will not recognize the callback listener to be
15
removed.</p><p>See test case
16
<tt class="code">org.jboss.test.remoting.callback.push.MultipleCallbackServersTestCase</tt>
17
.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch12.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch14.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 12. How to use it - sample code </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 14. Compatibility and versioning</td></tr></table></div></body></html>
b'\\ No newline at end of file'