PipeServer Component
Properties Methods Events Config Settings Errors
The PipeServer component is a lightweight server component based on an asynchronous, event-driven architecture. It is designed to balance the load between connections for a fast, powerful server.
Syntax
nsoftware.IPWorksIPC.PipeServer
Remarks
PipeServer is the server complement of PipeClient (which is used to create client applications). They share a common design philosophy and interface. PipeServer is as easy to use as PipeClient.
The client connections are identified by a ConnectionId, an id generated by the component to identify each connection. This id is unique to each connection. PipeServer's events also have ConnectionId as a parameter to identify the connection to which they are related.
Our main goal in designing PipeServer was to make it easy to use without sacrificing performance. The component has a minimum of properties, and events: Connected, DataIn, Disconnected, ReadyToSend, and Error.
PipeServer can start to listen on a pipe by setting PipeName and then setting Listening to True. When a client connects the Connected event fires, a ConnectionId is assigned, and communication can start. From this point on, the operation is very similar to PipeClient.
Property List
The following is the full list of the properties of the component with short descriptions. Click on the links for further details.
Connections | A collection of currently connected clients. |
DefaultEOL | This property includes a default end-of-line (EOL) value to be used by incoming connections. |
DefaultMaxLineLength | The property includes the default maximum line length value for inbound connections. |
DefaultSingleLineMode | This property tells the component whether or not to treat new connections as line oriented. |
DefaultTimeout | This property includes an initial timeout value to be used by incoming connections. |
Listening | If True, the component accepts incoming connections. |
PipeName | The name of the pipe. |
Method List
The following is the full list of the methods of the component with short descriptions. Click on the links for further details.
Config | Sets or retrieves a configuration setting. |
Disconnect | This method disconnects the specified client. |
DoEvents | This method processes events from the internal message queue. |
Interrupt | This method interrupts a synchronous send to the remote host. |
Send | This method sends binary data to the specified client. |
SendBytes | This method sends binary data to the specified client. |
SendFile | This method sends the file to the remote host. |
SendLine | This method sends a string followed by a new line. |
SendText | This method sends text to the specified client. |
SetUploadStream | This method uploads the data in the specified stream. |
Shutdown | This method shuts down the server. |
StartListening | This method starts listening for incoming connections. |
StopListening | This method stops listening for new connections. |
Event List
The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.
Connected | Fired immediately after a connection completes. |
DataIn | This event is fired when data come in. |
Disconnected | Fires when a client disconnects. |
Error | This event fires information about errors during data delivery. |
ReadyToSend | Fired when the component is ready to send data. |
Config Settings
The following is a list of config settings for the component with short descriptions. Click on the links for further details.
CloseStreamAfterTransfer | If true, the component will close the upload or download stream after the transfer. |
CustomSecurityDescription | A custom security descriptor to define access to the pipe. |
InBufferSize | The size in bytes of the output buffer. |
OutBufferSize | The size in bytes of the input buffer. |
BuildInfo | Information about the product's build. |
GUIAvailable | Whether or not a message loop is available for processing events. |
LicenseInfo | Information about the current license. |
MaskSensitiveData | Whether sensitive data is masked in log messages. |
UseFIPSCompliantAPI | Tells the component whether or not to use FIPS certified APIs. |
UseInternalSecurityAPI | Whether or not to use the system security libraries or an internal implementation. |
Connections Property (PipeServer Component)
A collection of currently connected clients.
Syntax
public PipeConnectionMap Connections { get; }
Public ReadOnly Property Connections As PipeConnectionMap
Remarks
This property contains a collection of currently connected clients. All of the connections may be managed using this property. Each connection is described by the different fields of the PipeConnection type.
This collection is a hashtable type of collection, in which the Connection Id string is used as the key to the desired connection. The Connected event fires when a client connects and provides the Connection Id (key) that identifies the client.
Example (Broadcasting Data)
foreach (Connection c in pipeserver1.Connections.Values) {
c.DataToSend = "Broadcast Data";
}
This property is read-only.
Please refer to the PipeConnection type for a complete list of fields.DefaultEOL Property (PipeServer Component)
This property includes a default end-of-line (EOL) value to be used by incoming connections.
Syntax
Default Value
""
Remarks
This property contains a default end-of-line (EOL) value to be used by incoming connections. Once the component accepts and establishes an inbound connection, it will set that connection's EOL to the value in this property. By default, this value is empty (""), meaning that data will be fired as it is received.
DefaultMaxLineLength Property (PipeServer Component)
The property includes the default maximum line length value for inbound connections.
Syntax
Default Value
2048
Remarks
This property controls the default size of an internal buffer that holds received data while waiting for an end-of-line (EOL) string.
The minimum value for this property is 256 bytes. The default value is 2048 bytes.
DefaultSingleLineMode Property (PipeServer Component)
This property tells the component whether or not to treat new connections as line oriented.
Syntax
Default Value
False
Remarks
This property instructs the component whether or not to treat newly established connections as line-oriented protocols. If this value is True, newly accepted connections will read the incoming data stream as lines separated by a carriage return line feed (CRLF), carriage return (CR), or line feed (LF) and will ignore the end of lines (EOLs).
DefaultTimeout Property (PipeServer Component)
This property includes an initial timeout value to be used by incoming connections.
Syntax
Default Value
0
Remarks
This property is used by the component to set the operational timeout value of all inbound connections once they are established.
This property defines the timeout when sending data. When SSLEnabled is False, a value of 0 means data will be sent asynchronously, and a positive value means data is sent synchronously.
When SSLEnabled is True, all data are sent synchronously regardless of the Timeout value.
Listening Property (PipeServer Component)
If True, the component accepts incoming connections.
Syntax
Default Value
False
Remarks
Use this property to make the component 'listen' (accept connections) on the pipe specified by PipeName. Setting this property to False will make the component stop listening. Please note that this does not close any existing connections.
Use the StartListening and StopListening methods to control whether the component is listening.
This property is not available at design time.
PipeName Property (PipeServer Component)
The name of the pipe.
Syntax
Default Value
""
Remarks
This property specifies the name of the pipe on which to accept connections. Clients must use this name when establishing a connection to PipeServer.
Config Method (PipeServer Component)
Sets or retrieves a configuration setting.
Syntax
Remarks
Config is a generic method available in every component. It is used to set and retrieve configuration settings for the component.
These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.
To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).
To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.
Disconnect Method (PipeServer Component)
This method disconnects the specified client.
Syntax
public void Disconnect(string connectionId); Async Version public async Task Disconnect(string connectionId); public async Task Disconnect(string connectionId, CancellationToken cancellationToken);
Public Sub Disconnect(ByVal ConnectionId As String) Async Version Public Sub Disconnect(ByVal ConnectionId As String) As Task Public Sub Disconnect(ByVal ConnectionId As String, cancellationToken As CancellationToken) As Task
Remarks
Calling this method will disconnect the client specified by the ConnectionId parameter.
DoEvents Method (PipeServer Component)
This method processes events from the internal message queue.
Syntax
public void DoEvents(); Async Version public async Task DoEvents(); public async Task DoEvents(CancellationToken cancellationToken);
Public Sub DoEvents() Async Version Public Sub DoEvents() As Task Public Sub DoEvents(cancellationToken As CancellationToken) As Task
Remarks
When DoEvents is called, the component processes any available events. If no events are available, it waits for a preset period of time, and then returns.
Interrupt Method (PipeServer Component)
This method interrupts a synchronous send to the remote host.
Syntax
public void Interrupt(string connectionId); Async Version public async Task Interrupt(string connectionId); public async Task Interrupt(string connectionId, CancellationToken cancellationToken);
Public Sub Interrupt(ByVal ConnectionId As String) Async Version Public Sub Interrupt(ByVal ConnectionId As String) As Task Public Sub Interrupt(ByVal ConnectionId As String, cancellationToken As CancellationToken) As Task
Remarks
This property is called using the Connection Id if you wish to interrupt a connection and stop a file from uploading without disconnecting the client connected to the component. If you use SendFile to upload a file, the component will run synchronously on that Connection Id until it is completed.
Send Method (PipeServer Component)
This method sends binary data to the specified client.
Syntax
Remarks
This method sends binary data to the client identified by ConnectionId. To send text, use the SendText method instead.
When Timeout is set to 0 and SSLEnabled is set to False, the component will behave asynchronously. If you are sending data to the remote host faster than it can process it, or faster than the network's bandwidth allows, the outgoing queue might fill up. When this happens, the operation fails with exception 10035: "[10035] Operation would block" (WSAEWOULDBLOCK). You can check this error, and then try to send the data again. . The BytesSent property shows how many bytes were sent (if any). If 0 bytes were sent, then you can wait for the ReadyToSend event before attempting to send data again.
Note: The ReadyToSend event is not fired when part of the data is sent successfully.
When SSLEnabled is True or Timeout is set to a positive value, the component behaves synchronously.
SendBytes Method (PipeServer Component)
This method sends binary data to the specified client.
Syntax
Remarks
This method sends binary data to the client identified by ConnectionId. To send text, use the SendText method instead.
When Timeout is set to 0 and SSLEnabled is set to False, the component will behave asynchronously. If you are sending data to the remote host faster than it can process it, or faster than the network's bandwidth allows, the outgoing queue might fill up. When this happens, the operation fails with exception 10035: "[10035] Operation would block" (WSAEWOULDBLOCK). You can check this error, and then try to send the data again. . The BytesSent property shows how many bytes were sent (if any). If 0 bytes were sent, then you can wait for the ReadyToSend event before attempting to send data again.
Note: The ReadyToSend event is not fired when part of the data is sent successfully.
When SSLEnabled is True or Timeout is set to a positive value, the component behaves synchronously.
SendFile Method (PipeServer Component)
This method sends the file to the remote host.
Syntax
Remarks
This method sends the file to the client specified by the ConnectionId.
Note: This method operate synchronously. DefaultTimeout or Timeout must be set to a positive value before calling this method.
SendLine Method (PipeServer Component)
This method sends a string followed by a new line.
Syntax
Remarks
This method is used to send data with line-oriented protocols. The line is followed by CRLF ("\r\n") .
Please refer to the GetLine method and SingleLineMode property for more information.
SendText Method (PipeServer Component)
This method sends text to the specified client.
Syntax
Remarks
This method sends text to the client identified by ConnectionId. To send binary data, use the SendBytes method instead.
When Timeout is set to 0 and SSLEnabled is set to False, the component will behave asynchronously. If you are sending data to the remote host faster than it can process it, or faster than the network's bandwidth allows, the outgoing queue might fill up. When this happens, the operation fails with exception 10035: "[10035] Operation would block" (WSAEWOULDBLOCK). You can check this error, and then try to send the data again. . The BytesSent property shows how many bytes were sent (if any). If 0 bytes were sent, then you can wait for the ReadyToSend event before attempting to send data again.
Note: The ReadyToSend event is not fired when part of the data is sent successfully.
When SSLEnabled is True or Timeout is set to a positive value, the component behaves synchronously.
SetUploadStream Method (PipeServer Component)
This method uploads the data in the specified stream.
Syntax
public void SetUploadStream(string connectionId, System.IO.Stream stream); Async Version public async Task SetUploadStream(string connectionId, System.IO.Stream stream); public async Task SetUploadStream(string connectionId, System.IO.Stream stream, CancellationToken cancellationToken);
Public Sub SetUploadStream(ByVal ConnectionId As String, ByVal Stream As System.IO.Stream) Async Version Public Sub SetUploadStream(ByVal ConnectionId As String, ByVal Stream As System.IO.Stream) As Task Public Sub SetUploadStream(ByVal ConnectionId As String, ByVal Stream As System.IO.Stream, cancellationToken As CancellationToken) As Task
Remarks
This method uploads the data in the specified stream to the connection identified by ConnectionId. The component will automatically close this stream if CloseStreamAfterTransfer is true (default).
Shutdown Method (PipeServer Component)
This method shuts down the server.
Syntax
public void Shutdown(); Async Version public async Task Shutdown(); public async Task Shutdown(CancellationToken cancellationToken);
Public Sub Shutdown() Async Version Public Sub Shutdown() As Task Public Sub Shutdown(cancellationToken As CancellationToken) As Task
Remarks
This method shuts down the server. Calling this method is equivalent to calling StopListening and then breaking every client connection by calling Disconnect.
StartListening Method (PipeServer Component)
This method starts listening for incoming connections.
Syntax
public void StartListening(); Async Version public async Task StartListening(); public async Task StartListening(CancellationToken cancellationToken);
Public Sub StartListening() Async Version Public Sub StartListening() As Task Public Sub StartListening(cancellationToken As CancellationToken) As Task
Remarks
This method begins listening for incoming connections on the pipe specified by PipeName.
To stop listening for new connections, call StopListening. To stop listening for new connections and to disconnect all existing clients, call Shutdown.
StopListening Method (PipeServer Component)
This method stops listening for new connections.
Syntax
public void StopListening(); Async Version public async Task StopListening(); public async Task StopListening(CancellationToken cancellationToken);
Public Sub StopListening() Async Version Public Sub StopListening() As Task Public Sub StopListening(cancellationToken As CancellationToken) As Task
Remarks
This method stops listening for new connections. After being called, any new connection attempts will be rejected. Calling this method does not disconnect existing connections.
To stop listening and to disconnect all existing clients, call Shutdown instead.
Connected Event (PipeServer Component)
Fired immediately after a connection completes.
Syntax
public event OnConnectedHandler OnConnected; public delegate void OnConnectedHandler(object sender, PipeServerConnectedEventArgs e); public class PipeServerConnectedEventArgs : EventArgs { public string ConnectionId { get; } }
Public Event OnConnected As OnConnectedHandler Public Delegate Sub OnConnectedHandler(sender As Object, e As PipeServerConnectedEventArgs) Public Class PipeServerConnectedEventArgs Inherits EventArgs Public ReadOnly Property ConnectionId As String End Class
Remarks
This event fires immediately after a client connects. The ConnectionId parameter identifies the client connection.
DataIn Event (PipeServer Component)
This event is fired when data come in.
Syntax
public event OnDataInHandler OnDataIn; public delegate void OnDataInHandler(object sender, PipeServerDataInEventArgs e); public class PipeServerDataInEventArgs : EventArgs { public string ConnectionId { get; } public string Text { get; }
public byte[] TextB { get; } public bool EOL { get; } }
Public Event OnDataIn As OnDataInHandler Public Delegate Sub OnDataInHandler(sender As Object, e As PipeServerDataInEventArgs) Public Class PipeServerDataInEventArgs Inherits EventArgs Public ReadOnly Property ConnectionId As String Public ReadOnly Property Text As String
Public ReadOnly Property TextB As Byte() Public ReadOnly Property EOL As Boolean End Class
Remarks
Trapping the DataIn event is your only chance to get the data coming from the other end of the connection specified by ConnectionId. The incoming data are provided through the Text parameter.
EOL indicates whether or not the EOL string was found at the end of Text. If the EOL string was found, then EOL is True.
If Text is part of the data portion of length larger than either DefaultMaxLineLength or MaxLineLength with no EOL strings in it, then EOL is False. Please note that this means that one or more DataIn events with EOL set to False can be received during a connection.
If the EOL property is "" (empty string), then EOL can be disregarded (it is always True).
Note: Events are not re-entrant. Performing time-consuming operations within this event will prevent it from firing again in a timely manner and may affect overall performance.
Disconnected Event (PipeServer Component)
Fires when a client disconnects.
Syntax
public event OnDisconnectedHandler OnDisconnected; public delegate void OnDisconnectedHandler(object sender, PipeServerDisconnectedEventArgs e); public class PipeServerDisconnectedEventArgs : EventArgs { public string ConnectionId { get; } }
Public Event OnDisconnected As OnDisconnectedHandler Public Delegate Sub OnDisconnectedHandler(sender As Object, e As PipeServerDisconnectedEventArgs) Public Class PipeServerDisconnectedEventArgs Inherits EventArgs Public ReadOnly Property ConnectionId As String End Class
Remarks
This event fires when a client disconnects. The ConnectionId parameters identifies the client that is disconnected.
Error Event (PipeServer Component)
This event fires information about errors during data delivery.
Syntax
public event OnErrorHandler OnError; public delegate void OnErrorHandler(object sender, PipeServerErrorEventArgs e); public class PipeServerErrorEventArgs : EventArgs { public string ConnectionId { get; } public int ErrorCode { get; } public string Description { get; } }
Public Event OnError As OnErrorHandler Public Delegate Sub OnErrorHandler(sender As Object, e As PipeServerErrorEventArgs) Public Class PipeServerErrorEventArgs Inherits EventArgs Public ReadOnly Property ConnectionId As String Public ReadOnly Property ErrorCode As Integer Public ReadOnly Property Description As String End Class
Remarks
The Error event is fired in case of exceptional conditions during message processing. Normally, the component throws an exception.
ErrorCode contains an error code and Description contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.
ConnectionId indicates the connection for which the error is applicable.
ReadyToSend Event (PipeServer Component)
Fired when the component is ready to send data.
Syntax
public event OnReadyToSendHandler OnReadyToSend; public delegate void OnReadyToSendHandler(object sender, PipeServerReadyToSendEventArgs e); public class PipeServerReadyToSendEventArgs : EventArgs { public string ConnectionId { get; } }
Public Event OnReadyToSend As OnReadyToSendHandler Public Delegate Sub OnReadyToSendHandler(sender As Object, e As PipeServerReadyToSendEventArgs) Public Class PipeServerReadyToSendEventArgs Inherits EventArgs Public ReadOnly Property ConnectionId As String End Class
Remarks
The ReadyToSend event indicates that the underlying pipe is ready to accept data after a failed SendBytes. The event is also fired immediately after a connection to the remote host is established.
PipeConnection Type
A currently connected client.
Remarks
This type describes the connection of a client which is currently connected to the component. The connection may be managed using the different fields of this type.
Fields
AcceptData
bool (read-only)
Default: True
This field indicates whether data reception is currently enabled. When false, data reception is disabled and the DataIn event will not fire for the connection. Use the PauseData and ProcessData methods to pause and resume data reception.
BytesSent
int (read-only)
Default: 0
This field shows how many bytes were sent after calling Send or SendBytes. Please see Send or SendBytes for more information.
Note: This field will always return 0 when the component is operating in the synchronous mode (i.e., the Timeout property is set to a positive value).
Connected
bool
Default: False
This field is used to disconnect individual connections and/or show their status.
The Connected field may be set to false to close the connection.
Connected also shows the status of a particular connection (connected/disconnected).
Use the Connect and Disconnect methods to manage the connection.
ConnectionId
string (read-only)
Default: ""
This field contains an identifier generated by the component to identify each connection. This identifier is unique to this connection.
EOL
string
Default: ""
The EOL field is used to define boundaries in the input stream using the value of the field.
The EOL field is especially useful with ASCII files. By setting it to CRLF ("\r\n") , the incoming ASCII text stream can be split into lines. In this case, one event is fired for each line received (as well as in packet boundaries). The CRLF ("\r\n") . bytes are discarded.
The EOL field is a binary string. This means that it can be more than one byte long, and it can contain NULL bytes.
EOLB
byte []
Default: ""
The EOL field is used to define boundaries in the input stream using the value of the field.
The EOL field is especially useful with ASCII files. By setting it to CRLF ("\r\n") , the incoming ASCII text stream can be split into lines. In this case, one event is fired for each line received (as well as in packet boundaries). The CRLF ("\r\n") . bytes are discarded.
The EOL field is a binary string. This means that it can be more than one byte long, and it can contain NULL bytes.
MaxLineLength
int
Default: 2048
This field is the size of an internal buffer that holds received data while waiting for an EOL string.
If an EOL string is found in the input stream before MaxLineLength bytes are received, the DataIn event is fired with the EOL parameter set to True, and the buffer is reset.
If no EOL is found, and MaxLineLength bytes are accumulated in the buffer, the DataIn event is fired with the EOL parameter set to False, and the buffer is reset.
The minimum value for MaxLineLength is 256 bytes. The default value is 2048 bytes.
SingleLineMode
bool
Default: False
This field shows the special mode for line-oriented protocols. When SingleLineMode is True, the component treats the incoming data stream as lines separated by carriage return (CR), line feed (LF), or CRLF. The EOL property is ignored.
Timeout
int
Default: 0
This field specifies a timeout for the component.
This field defines the timeout when sending data. When SSLEnabled is False, a value of 0 means data will be sent asynchronously and a positive value means data will be sent synchronously. When SSLEnabled is True, all data is sent synchronously regardless of the Timeout value. Please see the following notes for details.
Plaintext
If the Timeout field is set to 0, all operations return immediately, potentially failing with a WOULDBLOCK error if data cannot be sent immediately.
If Timeout is set to a positive value, data is sent in a blocking manner and the component will wait for the operation to complete before returning control. The component will handle any potential WOULDBLOCK errors internally and automatically retry the operation for a maximum of Timeout seconds.
SSL
If the Timeout field is set to 0, all operations will run uninterrupted until successful completion or an error condition is encountered.
If Timeout is set to a positive value, the component will wait for the operation to complete before returning control.
Additional Notes
The component will use DoEvents to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not freeze and remains responsive.
If Timeout expires, and the operation is not yet complete, the component throws an exception.
Note: By default, all timeouts are inactivity timeouts, that is, the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received.
The default value for the Timeout field is 0 (asynchronous for plaintext, synchronous for SSL).
Constructors
public PipeConnection();
Public PipeConnection()
Config Settings (PipeServer Component)
The component accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.PipeServer Config Settings
Base Config Settings
In some non-GUI applications, an invalid message loop may be discovered that will result in errant behavior. In these cases, setting GUIAvailable to false will ensure that the component does not attempt to process external events.
- Product: The product the license is for.
- Product Key: The key the license was generated from.
- License Source: Where the license was found (e.g., RuntimeLicense, License File).
- License Type: The type of license installed (e.g., Royalty Free, Single Server).
- Last Valid Build: The last valid build number for which the license will work.
This setting only works on these components: AS3Receiver, AS3Sender, Atom, Client(3DS), FTP, FTPServer, IMAP, OFTPClient, SSHClient, SCP, Server(3DS), Sexec, SFTP, SFTPServer, SSHServer, TCPClient, TCPServer.
FIPS mode can be enabled by setting the UseFIPSCompliantAPI configuration setting to true. This is a static setting that applies to all instances of all components of the toolkit within the process. It is recommended to enable or disable this setting once before the component has been used to establish a connection. Enabling FIPS while an instance of the component is active and connected may result in unexpected behavior.
For more details, please see the FIPS 140-2 Compliance article.
Note: This setting is applicable only on Windows.
Note: Enabling FIPS compliance requires a special license; please contact sales@nsoftware.com for details.
Setting this configuration setting to true tells the component to use the internal implementation instead of using the system security libraries.
On Windows, this setting is set to false by default. On Linux/macOS, this setting is set to true by default.
If using the .NET Standard Library, this setting will be true on all platforms. The .NET Standard library does not support using the system security libraries.
Note: This setting is static. The value set is applicable to all components used in the application.
When this value is set, the product's system dynamic link library (DLL) is no longer required as a reference, as all unmanaged code is stored in that file.
Trappable Errors (PipeServer Component)
PipeServer Errors
401 | Failed to create event. |
402 | Failed to create security descriptor. |
403 | Error creating named pipe. |
404 | Error connecting to named pipe. |
405 | Error disconnecting named pipe. |
408 | Error sending data. |
410 | Invalid MaxLineLength value. |
411 | Error reading data. |
412 | Error invoking RegisterWaitForSingleObject. |
413 | Operation would block. |
414 | Named pipe does not exist. |
415 | Named pipe is already connected. |
416 | Error connecting to named pipe. |
417 | Named pipe not connected. |
419 | Unsupported operation, see error message for details. |
424 | Invalid ConnectionID. |