I think because there are many different ways to tackle this type of job. What the end goal of the application *is* would be important to know.
On top of what Wally has said another two options could be sshfs in place of his suggestion for NFS. It pretty much meets all the same basic requirements, and has a much smaller system footprint. Also, there are websockets, which again can be used depending on what the final goal is. . . . On Fri, Mar 11, 2016 at 9:50 AM, Wally Bkg <[email protected]> wrote: > I may be misunderstanding what you are trying to do, but it seems you want > the enhanced named-pipe behavior of Windows (working across a network > connection) on Linux. Its one of the few Windows "enhancements" I've > actually found useful over the years. But as far as I could tell, to get > this behavior on Linux (posix) you need to write client/server processes on > each end and connect them to your named-pipe in which case which case I > fail to see the point of putting the local named-pipes into the mix instead > of just reading/writing the network sockets. > > If length is not too great, and you want it confined to a local sub-net > (my usual case) I find UDP works great, but TCP ports automatically handle > a many details and inherently behave FIFO like a pipe would with automatic > error detection/correction and buffering with the cost of uncertain > latencies. > > There may be someway to make this work if you have a common NFS share > mounted on the systems, but NFS brings along a lot of baggage you probably > don't need. > > Hope this helps. > --wally. > > > On Thursday, March 10, 2016 at 7:53:24 AM UTC-6, Dhanesh Kothari wrote: >> >> >> In Linux, we create a pipe using mknod(). I would like to create a >> buffered pipe( of length L, say), on which a remote process can write into >> using socket. How can we associate one end of pipe to a socket? >> > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
