[lug] Named pipe and network tool?

[D. Stimits]

Chris Riddoch wrote:
> 
> Hi, everyone.
> 
> I'm looking for a tool that acts as an intermediary between a named
> pipe and a network socket.  Basically, it would read from the named
> pipe and send that data over the network to a server, and it would
> take responses from the server and send them into the named pipe.
> 
> Why? There's a program I'm documenting in the pilot-link package,
> pi-port, that acts as a server accepting connections to a pilot on the
> same computer -- connect your pilot-aware program to port 4386 on the
> machine with the pilot running pi-port, and you've got a network sync.
> 
> Problem is, most of the pilot-link tools, and many of the others, talk
> to the pilot by working directly with the serial or USB device.  If
> the program were made to talk to a named pipe, though, and the daemon
> could connect that to the server, there would be a flow of data
> something like this:
> 
> pilot <-> pi-port <-network-> *** <-> named pipe <-> application (e.g. jpilot)
> 
> Is this a sensible way of doing it?  And what's the program that fits
> in the *** spot?

One question...do you already have the "application" part that can
read/write from a named pipe?

D. Stimits, stimits at idcomm.com

> 
> Thanks in advance,
> 
> --
> Chris Riddoch         |  epistemological
> socket at peakpeak.com   |  humility
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug