Browse Prior Art Database

Use of Named Pipes in Reverse Fashion

IP.com Disclosure Number: IPCOM000105507D
Original Publication Date: 1993-Aug-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 2 page(s) / 33K

Publishing Venue

IBM

Related People

Dinella, T: AUTHOR [+2]

Abstract

A method is defined to reverse the direction of communication flow on a named pipe.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 96% of the total text.

Use of Named Pipes in Reverse Fashion

      A method is defined to reverse the direction of communication
flow on a named pipe.

      A remote named pipe is shared by a LAN Server or a Peer Server.
LAN clients may connect to the shared named pipe.  The direction of
communication, then, is normally from client to server.

      To do remote performance monitoring support in a LAN
environment, a Remote Named Pipe may be used as provided by the
underlying operating system (OS/2* 2.0 and LAN Server 2.0).  The goal
is to monitor a LAN Requester from a LAN Server or Peer Server.
However, the Remote Named Pipe support has an implied "direction" --
which is opposite the direction we want to go.

      In our case we must establish a remote named pipe from the
server.  Then the initial direction of communication is from server
to client.  To accomplish this reversed named pipe, a daemon process
is started in the client.  Using the NetBIOS protocol, the daemon
process listens for broadcast messages from the Server that instruct
it to attach to the Server's remote named pipe.  When such a
broadcast message is received, the client connects to the Server's
shared remote named pipe.  Now the Server can communication with the
client in the reverse direction.

      A prior solution in OS/2 System Performance Monitor/2 Version
1.0 used a remote named pipe from client to server.  This new
solution allows a system administrator to monitor not just remote LAN
serv...