Named Pipe Channel

From RemObjects Software

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

This channel provides communication between a client and server using Windows Named Pipes feature. Named pipe is recommended for communications between processes on the same computer, especially when run via separate users. This could be useful, for example for service control.

Please refer to the MSDN documentation on Named Pipes for more details.

Tip: one important to bear in mind: Windows has a set limit for the number of clients connected to a named pipe at once - 5 for Home, 10 for Pro. TCP/IP is a better alternative if you want to run a network server.

Client Channel Components

• NamedPipeClientChannel (.NET) ('Vinci')
• TRONamedPipeChannel (Delphi)

Server Channel Components

• NamedPipeServerChannel (.NET) ('Vinci')
• TRONamedPipeServer (Delphi)

See Also

• Super TCP Channel
• Super HTTP Channel ('Vinci')
• HTTP Channel
• TCP Channel (legacy)
• Local Channel
• UDP and Broadcast Channels (Delphi only)
• 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