Channel components are the heart of Remoting SDK. They connect your client applications and your server applications by sending Messages back and forth, to submit a request, return a response, fire a callback event, etc. No matter what type of application you are building with Remoting SDK, channels will be an integral part of it.
To accommodate for a wide variety of scenarios and provide flexibility, Remoting SDK includes a pretty extensive list of channel components, which in some cases might be difficult to choose for the novice user. See the Comparison of the Remoting SDK Channels article for a brief overview of all available channel types.
Note: for historic reasons, the Remoting SDK for Delphi class library uses the terminology "Channel" for client channels and "Server" for server channels, while the .NET and Cocoa editions properly refer to "client channel" and "server channel". Besides these naming differences, the same concepts apply for both platforms.
Commonly Used Channels
- HTTP Channel – flexible and network independent communication using the World Wide Web's Hypertext Transfer Protocol (HTTP).
- Super TCP Channel – sophisticated and flexible two-way communication between clients and servers.
- Super HTTP Channel – combining the flexibility of HTTP with the power of the Super TCP Channel.
Frequently Used Channels
- Legacy TCP Channel – lightweight communication over raw TCP.
- Email Channel – asynchronous communication over existing email infrastructure (Delphi only).
- Local Channel – direct communication within the same application.
- DLL Channel - implements server logic inside a DLL and accesses it using the standard Remoting SDK calling mechanisms (Delphi only).
Rarely Used Channels
- UDP and Broadcast Channels – lightweight packet based communication (Delphi only).
- Named Pipe Channel – inner-LAN communication without TCP/IP network protocol.
- WinMessage Channel – inter-process communication without network on a local computer (Delphi only).