Struct ipworksipc::PipeClient

Properties   Methods   Events   Config Settings   Errors  

The PipeClient struct is a simple client for connecting and communicating over named pipes.

Syntax

ipworksipc::PipeClient

Remarks

The PipeClient struct is used to connect to an existing pipe server. After connecting the transfer of data is handled very similarly to socket communication.

To begin, first set pipe_name to the name of the pipe to which the connection will be made. Call connect or set on_connected to True to establish the connection. The on_connected event will fire when the connection is complete.

After connecting call send or send_file to send data. Incoming data is received through the on_data_in event.

To disconnect call disconnect or set connected to False.

Synchronous and Asynchronous Operation

If the timeout property is set to 0, the struct will behave asynchronously and all operations return immediately, potentially failing with an error if they can't be completed immediately.

If timeout is set to a positive value, the struct will behave synchronously and wait for the operation to complete before returning control.

The struct will use do_events 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 struct fails with an error.

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 property is 60 seconds.

Object Lifetime

The new() method returns a mutable reference to a struct instance. The object itself is kept in the global list maintained by IPWorksIPC. Due to this, the PipeClient struct cannot be disposed of automatically. Please, call the dispose(&self) method of PipeClient when you have finished using the instance.

Property List

---

The following is the full list of the properties of the struct with short descriptions. Click on the links for further details.

Method List

---

The following is the full list of the methods of the struct with short descriptions. Click on the links for further details.

Event List

---

The following is the full list of the events fired by the struct with short descriptions. Click on the links for further details.

Config Settings

---

The following is a list of config settings for the struct with short descriptions. Click on the links for further details.

accept_data property (PipeClient Struct)

This property indicates whether data reception is currently enabled.

Syntax

fn accept_data(&self) -> Result<bool, IPWorksIPCError> 

Default Value

true

Remarks

This property indicates whether data reception is currently enabled. When false, data reception is disabled and the on_data_in event will not fire. Use the pause_data and process_data methods to pause and resume data reception.

This property is read-only.

Data Type

bool

bytes_sent property (PipeClient Struct)

This property includes the number of bytes actually sent after a call to the SendBytes method.

Syntax

fn bytes_sent(&self) -> Result<i32, IPWorksIPCError> 

Default Value

0

Remarks

This property indicates how many bytes were sent after the last call to send_bytes. Please check the send_bytes method for more information.

NOTE: that bytes_sent will always return 0 when the struct is operating in synchronous mode (i.e., the timeout property is set to a positive value.)

This property is read-only.

Data Type

i32

connected property (PipeClient Struct)

Triggers a connection or disconnection.

Syntax

fn connected(&self) -> Result<bool, IPWorksIPCError> 

Default Value

false

Remarks

This property triggers a connection or disconnection. Setting this property to True makes the struct attempt to connect to the pipe identified by the pipe_name property. If successful, after the connection is achieved the value of the property changes to True and the on_connected event is fired.

Setting this property to False closes the connection.

This property is read-only.

Data Type

bool

eol property (PipeClient Struct)

This property is used to break the incoming data stream into chunks separated by EOL .

Syntax

fn eol(&self) -> Result<Vec<u8>, IPWorksIPCError> 
fn set_eol(&self, value : Vec<u8>) ->  Option<IPWorksIPCError> 
fn set_eol_ref(&self, value : &[u8]) ->  Option<IPWorksIPCError> 

Default Value

""

Remarks

This property is used to define boundaries in the input stream using the value of the property.

This property is especially useful with ASCII files. Setting it to CRLF ("\r\n") enables the incoming ASCII text stream to split into defined 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.

This property is a binary string. Notably, this means that it can be more than one byte long, and it can contain NULL bytes.

Data Type

Vec<u8>

pipe_name property (PipeClient Struct)

The name of the pipe.

Syntax

fn pipe_name(&self) -> Result<String, IPWorksIPCError> 
fn set_pipe_name(&self, value : &str) ->  Option<IPWorksIPCError> 
fn set_pipe_name_ref(&self, value : &String) ->  Option<IPWorksIPCError> 

Default Value

""

Remarks

This property specifies the name of the pipe.

This may be the name by itself, for instance "MyPipe", or in the format "\\.\pipe\MyPipe".

Data Type

String

record_length property (PipeClient Struct)

The length of received data records.

Syntax

fn record_length(&self) -> Result<i32, IPWorksIPCError> 
fn set_record_length(&self, value : i32) ->  Option<IPWorksIPCError> 

Default Value

0

Remarks

If set to a positive value, this property defines the length of data records to be received. The struct will accumulate data until RecordLength is reached and only then fire the on_data_in event with data of length RecordLength. This allows data to be received as records of known length. This value can be changed at any time, including within the on_data_in event.

The default value is 0, meaning this property is not used.

Data Type

i32

single_line_mode property (PipeClient Struct)

This property includes a special mode for line-oriented protocols.

Syntax

fn single_line_mode(&self) -> Result<bool, IPWorksIPCError> 
fn set_single_line_mode(&self, value : bool) ->  Option<IPWorksIPCError> 

Default Value

false

Remarks

When this property is set to True, the struct treats the incoming data stream as lines separated by carriage return line feed (CRLF), CR, or LF. The eol property is ignored.

When this property is set to True, accept_data automatically will be set to False. Please refer to the get_line method for more information.

Data Type

bool

timeout property (PipeClient Struct)

This property includes the timeout for the struct.

Syntax

fn timeout(&self) -> Result<i32, IPWorksIPCError> 
fn set_timeout(&self, value : i32) ->  Option<IPWorksIPCError> 

Default Value

60

Remarks

If the timeout property 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 struct will wait for the operation to complete before returning control. The struct will handle any potential WOULDBLOCK errors internally and automatically retry the operation for a maximum of timeout seconds.

The struct will use do_events 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 struct fails with an error.

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 property is 60 seconds.

Data Type

i32

config method (PipeClient Struct)

Sets or retrieves a configuration setting.

Syntax

fn config(&self, configuration_string : &str) -> Result<String, IPWorksIPCError>

Remarks

config is a generic method available in every struct. It is used to set and retrieve configuration settings for the struct.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the struct, 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.

connect method (PipeClient Struct)

Connects to a named pipe.

Syntax

fn connect(&self) -> Result<(), IPWorksIPCError>

Remarks

This method connects to a named pipe specified by pipe_name. Calling this method is equivalent to setting the connected property to True.

Example (Connecting)

PipeClient.PipeName = "MyPipe"; PipeClient.Connect();

disconnect method (PipeClient Struct)

Disconnects from the named pipe.

Syntax

fn disconnect(&self) -> Result<(), IPWorksIPCError>

Remarks

This method disconnects from the pipe. Calling this method is equivalent to setting the connected property to False.

do_events method (PipeClient Struct)

This method processes events from the internal message queue.

Syntax

fn do_events(&self) -> Result<(), IPWorksIPCError>

Remarks

When do_events is called, the struct processes any available events. If no events are available, it waits for a preset period of time, and then returns.

get_line method (PipeClient Struct)

This method gets a line of text from the server.

Syntax

fn get_line(&self) -> Result<String, IPWorksIPCError>

Remarks

This method gets a line of text from the server. This method is an alternative method of receiving data for line-oriented protocols. The struct will block if necessary and then will return the received line. accept_data will be set automatically to True when the method is called, and then will be set to False after a line is received.

Please refer to the single_line_mode property for more information.

interrupt method (PipeClient Struct)

This method interrupts the current action.

Syntax

fn interrupt(&self) -> Result<(), IPWorksIPCError>

Remarks

This method interrupts the current action. If you use send_file to upload a file, the struct will run synchronously until the upload is completed. This method will allow you to stop the file from uploading without disconnecting from the host.

process_data method (PipeClient Struct)

This method reenables data reception after a call to PauseData .

Syntax

fn process_data(&self) -> Result<(), IPWorksIPCError>

Remarks

This method reenables data reception after a previous call to pause_data. When pause_data is called, the on_data_in event will not fire. To reenable data reception and allow on_data_in to fire, call this method.

NOTE: This method is used only after previously calling pause_data. It does not need to be called to process incoming data by default.

send method (PipeClient Struct)

Sends data over the connected pipe.

Syntax

fn send(&self, text : &[u8]) -> Result<(), IPWorksIPCError>

Remarks

This method sends data to the server.

send_bytes method (PipeClient Struct)

This method sends binary data over the connected pipe.

Syntax

fn send_bytes(&self, data : &[u8]) -> Result<(), IPWorksIPCError>

Remarks

This method sends the specified binary data to the server. To send text, use the send_text method instead.

When timeout is set to 0 the struct will behave asynchronously. If you are sending data to the receiving process faster than it can process it, the outgoing queue might fill up. When this happens, the struct fails with error 10035: "[10035] Operation would block" (WSAEWOULDBLOCK). You can check this error, and then try to send the data again. The bytes_sent property shows how many bytes were sent (if any). If 0 bytes were sent, then you can wait for the on_ready_to_send event before attempting to send data again. (However, please note that on_ready_to_send is not fired when part of the data is successfully sent).

send_file method (PipeClient Struct)

Sends the file over the connected pipe.

Syntax

fn send_file(&self, file_name : &str) -> Result<(), IPWorksIPCError>

Remarks

This method sends the specified file to the server/process over the connected pipe.

Timeout must be set to a positive value so that the struct will operate synchronously.

send_line method (PipeClient Struct)

This method sends a string followed by a newline.

Syntax

fn send_line(&self, text : &str) -> Result<(), IPWorksIPCError>

Remarks

This method sends a string followed by a newline. This method is used to send data with line-oriented protocols. The line is followed by CRLF ("\r\n") .

Please refer to the get_line method and single_line_mode property for more information.

send_text method (PipeClient Struct)

This method sends text over the connected pipe.

Syntax

fn send_text(&self, text : &str) -> Result<(), IPWorksIPCError>

Remarks

This method sends the specified text to the server. To send binary data, use the send_bytes method instead.

When timeout is set to 0 the struct will behave asynchronously. If you are sending data to the receiving process faster than it can process it, the outgoing queue might fill up. When this happens, the struct fails with error 10035: "[10035] Operation would block" (WSAEWOULDBLOCK). You can check this error, and then try to send the data again. The bytes_sent property shows how many bytes were sent (if any). If 0 bytes were sent, then you can wait for the on_ready_to_send event before attempting to send data again. (However, please note that on_ready_to_send is not fired when part of the data is successfully sent).

on_connected event (PipeClient Struct)

Fired immediately after a connection completes.

Syntax

// PipeClientConnectedEventArgs carries the PipeClient Connected event's parameters.
pub struct PipeClientConnectedEventArgs {
}

// PipeClientConnectedEvent defines the signature of the PipeClient Connected event's handler function.
pub trait PipeClientConnectedEvent {
  fn on_connected(&self, sender : PipeClient, e : &mut PipeClientConnectedEventArgs);
}

impl <'a> PipeClient<'a> {
  pub fn on_connected(&self) -> &'a dyn PipeClientConnectedEvent;
  pub fn set_on_connected(&mut self, value : &'a dyn PipeClientConnectedEvent);
  ...
}

Remarks

When the connection is successfully established this event will fire.

on_data_in event (PipeClient Struct)

This event is fired when data (complete lines) come in.

Syntax

// PipeClientDataInEventArgs carries the PipeClient DataIn event's parameters.
pub struct PipeClientDataInEventArgs {
  fn text(&self) -> &[u8]
  fn eol(&self) -> bool
}

// PipeClientDataInEvent defines the signature of the PipeClient DataIn event's handler function.
pub trait PipeClientDataInEvent {
  fn on_data_in(&self, sender : PipeClient, e : &mut PipeClientDataInEventArgs);
}

impl <'a> PipeClient<'a> {
  pub fn on_data_in(&self) -> &'a dyn PipeClientDataInEvent;
  pub fn set_on_data_in(&mut self, value : &'a dyn PipeClientDataInEvent);
  ...
}

Remarks

Trapping the on_data_in event is your only chance to get the data coming from the other end of the connection. 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 a data portion of length larger than MaxLineLength with no eol strings in it, then EOL is False. NOTE: This means that one or more on_data_in 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.

on_disconnected event (PipeClient Struct)

Fired when a connection is closed.

Syntax

// PipeClientDisconnectedEventArgs carries the PipeClient Disconnected event's parameters.
pub struct PipeClientDisconnectedEventArgs {
}

// PipeClientDisconnectedEvent defines the signature of the PipeClient Disconnected event's handler function.
pub trait PipeClientDisconnectedEvent {
  fn on_disconnected(&self, sender : PipeClient, e : &mut PipeClientDisconnectedEventArgs);
}

impl <'a> PipeClient<'a> {
  pub fn on_disconnected(&self) -> &'a dyn PipeClientDisconnectedEvent;
  pub fn set_on_disconnected(&mut self, value : &'a dyn PipeClientDisconnectedEvent);
  ...
}

Remarks

When the connection is closed this event will fire.

on_error event (PipeClient Struct)

Fired when information is available about errors during data delivery.

Syntax

// PipeClientErrorEventArgs carries the PipeClient Error event's parameters.
pub struct PipeClientErrorEventArgs {
  fn error_code(&self) -> i32
  fn description(&self) -> &String
}

// PipeClientErrorEvent defines the signature of the PipeClient Error event's handler function.
pub trait PipeClientErrorEvent {
  fn on_error(&self, sender : PipeClient, e : &mut PipeClientErrorEventArgs);
}

impl <'a> PipeClient<'a> {
  pub fn on_error(&self) -> &'a dyn PipeClientErrorEvent;
  pub fn set_on_error(&mut self, value : &'a dyn PipeClientErrorEvent);
  ...
}

Remarks

The on_error event is fired in case of exceptional conditions during message processing. Normally the struct fails with an error.

The error_code parameter contains an error code, and the description parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.

on_ready_to_send event (PipeClient Struct)

Fired when the struct is ready to send data.

Syntax

// PipeClientReadyToSendEventArgs carries the PipeClient ReadyToSend event's parameters.
pub struct PipeClientReadyToSendEventArgs {
}

// PipeClientReadyToSendEvent defines the signature of the PipeClient ReadyToSend event's handler function.
pub trait PipeClientReadyToSendEvent {
  fn on_ready_to_send(&self, sender : PipeClient, e : &mut PipeClientReadyToSendEventArgs);
}

impl <'a> PipeClient<'a> {
  pub fn on_ready_to_send(&self) -> &'a dyn PipeClientReadyToSendEvent;
  pub fn set_on_ready_to_send(&mut self, value : &'a dyn PipeClientReadyToSendEvent);
  ...
}

Remarks

The on_ready_to_send event indicates that the underlying pipe is ready to accept data again after a failed send. The event is also fired immediately after a connection to the remote host is established.

Config Settings (PipeClient Struct)

The struct 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 struct, access to these internal properties is provided through the config method.

PipeClient Config Settings

Base Config Settings

Trappable Errors (PipeClient Struct)

PipeClient Errors