The service code, the remote code being executed by the caller, does its thing
and returns the results back through the same flow in reverse.
Note the demarcation line showing the interface provided by the service code. Also note
the callout up top noting the apparent call flow. As far as the caller is concerned, the interface
to the remote code is identical to what it would be if it were running in the same process
space; therefore, the apparent flow from the perspective of the client code doesn??™t include
anything below the demarcation because that all happens transparently. The same is true of
the code being remoted.
CHAPTER 2 n GETTING TO KNOW DWR 45
Figure 2-1. Architectural overview of RPC
DWR is simply a particular implementation of this diagram. We??™ll look at the specific parts
in the next section, but for now, that??™s the pertinent point to grep from all this. That and the
fact that DWR will save you a tremendous amount of time and energy!
Another key point about DWR is that it??™s a very nonintrusive tool to use. What I mean by
this is that it doesn??™t force any required architecture down your throat in terms of how you
organize your server-side code or your client-side code.
Pages:
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127