Switching from HTTP to TCP Communication
The HTTP protocol is ideal when trying to send data through firewalls or over the Internet, but when your goal is to achieve the maximum communication speed, TCP communication will probably be a better candidate. .NET remoting allows you to switch communication channels by simply changing a few configuration parameters.
Note
The server configuration file shown in Listing 30.16 instructs the server to listen for HTTP messages on port 8099 and TCP messages on port 8231.
The client is instead configured to use HTTP messages because of the value of the url attribute in the well-known node (http://localhost:8099/SimpleFactory.soap).
To make it use a TCP channel, simply change that to "tcp://localhost:8231/SimpleFactory.soap" ...
Get Delphi for .NET Developer’s Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
