NamedPipeClientChannel Class

This is a Library topic for RemObjects SDK for .NET
This page is generated from external data, please do not update
Namespaces — Interfaces — Classes — Enums — Implements
Contents |
Overview
The NamedPipeClientChannel uses Windows Named Pipes to communicate between client and server on the same machine or local network. Named Pipes are recommended for communications between processes on the same computer, especially when run by separate users.
Please refer to the MSDN documentation on Named Pipes for more details.
Location
- Assembly: RemObjects.SDK.dll
- Namespace: RemObjects.SDK
- Ancestry: System.ComponentModel.Component | Channel | ClientChannel | NamedPipeClientChannel
Implemented interfaces
Constants
| URL_SCHEMES_NOT_SUPPORTED protected (declared in ClientChannel) |
|---|
|
|
Properties
| Busy (declared in ClientChannel) |
|---|
|
Busy is true if the transport channel is currently busy with an operation. Otherwise Busy is false. By default, if the transport channel is busy, it will not attempt to process another request and a ChannelBusyException exception is raised if you try to do so.
|
| HasAfterReceiveStream protected (declared in Channel) |
|
|
| HasBeforeSendStream protected (declared in Channel) |
|
|
| HasOnTransferProgress protected (declared in ClientChannel) |
|
|
| NetworkByteOrder |
|
Defines an order of transferring bytes. If true, the channel uses big-endian when transferring the data.
|
| Path |
|
Defines the unique name of the server to use. The name must match the Path property specified on the NamedPipeServerChannel in the server application.
|
| Server |
|
Specifies the name of the host running the server. This can be a host name or IP address on the local net, or "." (default), which indicates the local machine.
|
| TargetUri |
|
|
| TargetUrl (declared in ClientChannel) |
|
|
Class Methods
| BuildTargetUri protected (declared in ClientChannel) |
|---|
|
|
| ChannelMatchingTargetUri (String): IClientChannel (declared in ClientChannel) |
|
|
| ChannelMatchingTargetUri (Uri): IClientChannel (declared in ClientChannel) |
|
|
Instance Methods
| constructor |
|---|
|
Creates a new NamedPipeClientChannel instance.
|
| AsyncDispatch (declared in ClientChannel) |
|
|
| BeforeDispatch protected (declared in ClientChannel) |
|
|
| BeginDispatch (IMessage, AsyncCallback, Boolean, Object): IClientAsyncResult protected (declared in ClientChannel) |
|
|
| BeginDispatch (IMessage, AsyncCallback, Object): IClientAsyncResult (declared in ClientChannel) |
|
|
| CheckChannelBusy protected (declared in ClientChannel) |
|
|
| Clone |
|
Creates and returns a new NamedPipeClientChannel instance that is an identical copy of the current channel.
|
| CopyProperties (Channel) protected (declared in Channel) |
|
|
| CopyProperties (ClientChannel) protected |
|
Copies the properties from the given client channel.
|
| Dispatch (declared in ClientChannel) |
|
The implementation of IClientChannel.Dispatch. This method ensures the transport is not busy before calling IntDispatch and passing the given IMessage. If the transport is busy, a ChannelBusyException is thrown.
|
| EndDispatch (declared in ClientChannel) |
|
|
| IntDispatch protected |
|
This method connects to the server, using Path and Server values, dispatches request messages to the server for processing and eventually gets a response stream back.
|
| TriggerAfterReceiveStream protected (declared in Channel) |
|
|
| TriggerBeforeSendStream protected (declared in Channel) |
|
|
| TriggerOnException protected (declared in ClientChannel) |
|
|
| TriggerOnLoginNeeded protected (declared in ClientChannel) |
|
|
| TriggerOnTransferEnd protected (declared in ClientChannel) |
|
|
| TriggerOnTransferProgress protected (declared in ClientChannel) |
|
|
| TriggerOnTransferStart protected (declared in ClientChannel) |
|
|
Events
| AfterReceiveStream (declared in Channel) |
|---|
|
This event is triggered by client and server channels directly after a request or response stream has been received and before the stream gets parsed into a message. User code can assign handlers to this event to process, inspect or modify incoming messages, before they get handled by the RemObjects SDK framework. The passed Stream is a MemoryStream and may be modified. If no handlers are assigned to the AfterReceiveStream event, the message will load the data directly from the incoming medium (usually the network stream); assigning event handlers to AfterReceiveStream will induce a slight overhead as the data will first be copied into a local memory buffer for the event handler. This should not have any noticeably effect except for very large messages or on resource-limited systems such as Compact Framework Clients, but if utmost performance is important, take this note into consideration.
C#: event StreamEventHandler AfterReceiveStream VB: Event AfterReceiveStream As StreamEventHandler
|
| BeforeSendStream (declared in Channel) |
|
This event is triggered by client and server channels directly before a request or response stream will be sent over the network. User code can assign handlers to this event to process, inspect or modify incoming messages before they get sent out to the remote system. The passed Stream is a MemoryStream and may be modified.
C#: event StreamEventHandler BeforeSendStream VB: Event BeforeSendStream As StreamEventHandler
|
| OnException (declared in ClientChannel) |
|
This event is raised if an exception occurs during the execution of a remote request through the channel. The event will be raised both for exceptions originating from the server and for exceptions during communication (such as unavailability of the server). Attach a handler to this event to do custom handling of events without having to reply on explicit try/catch blocks in the calling code.
C#: event RequestExceptionEventHandler OnException VB: Event OnException As RequestExceptionEventHandler
|
| OnLoginNeeded (declared in ClientChannel) |
|
This event is raised if an SessionNotFoundException occurs during the execution of a remote request through the channel. The event gives you the opportunity to perform a login on the server (for example by calling a custom Login method, and then retry the call by setting the EventArgs' LoginSuccessful property to true. This way, your client can recover from a timed-out session to automatically logging in again, without the calling code having to consider the handling of SessionNotFoundExceptions manually.
C#: event LoginNeededEventHandler OnLoginNeeded VB: Event OnLoginNeeded As LoginNeededEventHandler
|
| OnTransferEnd (declared in ClientChannel) |
|
This event is triggered by the client channel after a transfer is completed (either the sending of a request or the receiving of a response).
C#: event TransferEndEventHandler OnTransferEnd VB: Event OnTransferEnd As TransferEndEventHandler
|
| OnTransferProgress (declared in ClientChannel) |
|
This event is triggered by the client channel during a transfer (either the sending of a request or the receiving of a response) whenever a new block of data has been sent or received.
C#: event TransferProgressEventHandler OnTransferProgress VB: Event OnTransferProgress As TransferProgressEventHandler
|
| OnTransferStart (declared in ClientChannel) |
|
This event is triggered by the client channel when a transfer (either the sending of a request or the receiving of a response) is about to be started.
C#: event TransferStartEventHandler OnTransferStart VB: Event OnTransferStart As TransferStartEventHandler |
See Also
- Lists
- RemObjects SDK for .NET: Namespaces — Interfaces — Classes — Enums — Implements
- RemObjects SDK shared: Data Types – File Types
- other editions
- RemObjects SDK for Xcode: Protocols — Classes — Enums — Aliases — Implements
- RemObjects SDK for Delphi: Interfaces — Classes — Aliases — Implements
- RemObjects SDK for Java: Namespaces — Interfaces — Classes — Enums — Implements
- RemObjects SDK for JavaScript: Objects

Product: RemObjects SDK
Available Editions: RemObjects SDK for .NET, Xcode, Delphi, Java and JavaScript