Pipe Server

The Pipe Server plugin simplifies the process of testing named pipe communications. It allows developers to quickly create a server-side pipe that client applications can connect to, streamlining setup and reducing the time and effort required for testing and debugging.

Capabilities

Required

org.jancy.io.win.named-pipe
 Allows users to create Windows named pipe servers.

Basic Setup

  1. In IO Ninja, click the “New Session” dropdown and select a new “Pipe Server” session
_images/pipe-server-new-session.png
  1. Enter the name of your pipe in the “Pipe:” field.
_images/pipe-server-pipe-name.png
  1. Press the “Start Listening” button, to the right of the “Pipe:” field.
_images/pipe-server-listening.png
  1. See connected clients in the “Active client(s)” section of the Control pane.
_images/pipe-server-clients.png
  1. In the Transmit pane, send messages as required.
_images/pipe-server-transmit.png
  1. Analyze messages received from clients in the log.
_images/pipe-server-replies.png
  1. In the Control pane, use “Client log filter:” to select which client you want to see messages from.
_images/pipe-server-filter.png

Settings

_images/pipe-server-settings.png
Setting Description Default
Pipe name Specify the pipe name to listen on.  
Message mode Enable or disable “message mode”, which allows read and write. False
Read parallelism Maximum number of read requests to submit to tdevmon at the same time. Having more than one pending read at a time helps prevent notification loss in IO-intensive scenarios (after filling one user buffer, tdevmon can immediately switch to the next one without any waiting). Increasing this number beyond 4 usually won’t yield any extra gains. 4
Read block size (B) The size of each individual read block submitted to tdevmon. 4KB
RX buffer size (B) The full size of the incoming data (RX) buffer. Affects read throughput. 16KB
TX buffer size (B) The full size of the outbound data (TX) buffer. Affects write throughput. 16KB
Keep read block size Don’t merge read blocks in RX buffer. Incoming data blocks coming in quick succession can be merged together so that IO Ninja writes them to log as a whole. When this option is set to True, blocks are written to the log without merging, i.e., exactly as they are received from the underlying transport.. False
Keep write block size Don’t merge write blocks in TX buffer. Outbound data blocks sent in quick succession can be merged together before submission to the underlying transport. When this option is set to True, blocks are submitted to the transport without merging, i.e., exactly as they are sent by the Transmit or Script panes.. False
RX buffer full notifications Toggle warnings in log about the incoming data (RX) buffer getting full. False