28 lines
1.2 KiB
HTML
28 lines
1.2 KiB
HTML
|
<html>
|
||
|
|
<head>
|
||
|
|
<link rel="stylesheet" type="text/css" href="..\styles.css">
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<img src="..\..\ro.png" alt="" align="right">
|
||
|
|
|
||
|
|
<!-------------------------------------------------------------------------->
|
||
|
|
|
||
|
|
<p class="h1">
|
||
|
|
<span>Proxy Server Sample</span>
|
||
|
|
</p>
|
||
|
|
|
||
|
|
|
||
|
|
<h2>Purpose</h2>
|
||
|
|
|
||
|
|
<p>This example shows how to create a proxy server to redirect the calls to another
|
||
|
|
server without having to recreate the RODL file, thus allowing the use of the same types of the original server.<br>
|
||
|
|
This provides total control. As every call will pass from the proxy class before going to the real server, you can even stop methods from being dispatched any further.</p>
|
||
|
|
|
||
|
|
<p>
|
||
|
|
<b>ProxyServer_ProxyServer_Impl</b> was created by simply copying the original <b>MainService_Impl.pas</b> file, renaming the <b>TMainService class</b> to <b>TProxyService</b> followed by implementing a bypass for all the method calls. This class is basically a server which accesses a RemObjects SDK server as a client would do.
|
||
|
|
</p>
|
||
|
|
<h2>Getting Started</h2>
|
||
|
|
Launch both servers and run the client. <br>
|
||
|
|
The client allows you to select either server. When you execute a method using the Proxy Server, you will see both servers log the call.
|
||
|
|
</body>
|
||
|
|
</html>
|