Check out the new USENIX Web site. next up previous
Next: Execution of TORBA Proxies Up: The TORBA Proposal Previous: Generated Proxy Implementation

Using TORBA Proxies

Figure 9 presents, in OMG IDLscript, the use of lookup proxy presented in the previous section. The first line instantiates the lookup proxy class. The second line invokes the query operation to find color printers faster than two pages per minute. This operation realizes the same search processing as the one presented in Figure 4. Simplicity brought up by TORBA becomes clear. The application developer does not bother with the trader technicity, he/she can focus on the use of the trading contract only. Moreover, the operation execution cannot fail as types have been checked by the TDL compiler. It can only return an empty sequence if no offer matches the search. The third line illustrates the option of using a search operation not defined in the trading contract: Searching offers related to B&W printers faster than ten pages per minute, for a cost less than five cents a page. Nevertheless, even if the use of this operation is provided, software engineering quality is improved when all the search requests are defined in the trading contract.

Figure 9: Printer Search Proxy Use.
\begin{figure}
\hrule\vskip 0.2cm
{\small\begin{verbatim}lookup = PrinterProx...
...LSE
and cost_per_page < 0.05 and ppm > 10'')\end{verbatim}}
\hrule\end{figure}


next up previous
Next: Execution of TORBA Proxies Up: The TORBA Proposal Previous: Generated Proxy Implementation
Raphael Marvie
2000-12-05