Legacy TCP Channel

From RemObjects Software

This is a RemObjects SDK Architecture entry
Feel free to add your notes to this topic below.

The TCP Channel has been superseded by the Super TCP Channel and it is recommended that the latter is used for all new applications.

TCP, the Transmission Control Protocol, is one of the two basic low-level protocols that form the basis of the internet with its TCP/IP network stack, and provides a stream based connection between a client and a server host. While TCP also provides the foundation for most more complex protocols such as HTTP, POP3 etc, the TCP Channel uses a lightweight protocol over raw TCP, introducing basically zero traffic overhead on top of the transmitted message data.

The TCP Channel is the perfect choice when traffic minimization is a must and firewalls are not an issue. The TCP channel will provide the best possible performance for method calls, in this scenario. On the Delphi side, the BPDX server channels provide the best performance and most flexibility, but can be more resource-hungry then the light-weight Indy server channels.

Client Channel Components

• IpTcpClientChannel (.NET)
• TROIndyTcpChannel (Delphi)

Server Channel Components

• IpTcpServerChannel (.NET)
• TROIndyTcpServer (Delphi)
• TROBPDXTcpServer (Delphi)

See Also

• Super TCP Channel
• Super HTTP Channel ('Vinci')
• HTTP Channel
• Local Channel
• UDP and Broadcast Channels (Delphi only)
• Named Pipe Channel
• DLL Channel (Delphi only)
• Email Channel (Delphi only)
• WinMessage Channel (Delphi only)
• Channel Compatibility
  • Client Channels
  • Server Channels
• Lists
  • Namespaces
  • Classes: .NET — Delphi
  • Interfaces: .NET — Delphi
  • Enums: .NET — Delphi
  • Types: Data — File

Product: RemObjects SDK
Current version: RemObjects SDK 'Vinci' (5.0)

Lists — Glossary — Features — How To — Components — Tools — Samples — Articles — Architecture — Issues