On Fri, Aug 9, 2013 at 6:45 PM, Geoff Shannon
I emailed the list a while ago that I was starting to work on a named pipe implementation for potential inclusion in the Boost.Interprocess library, and now I finally have some concrete evidence of progress. I've come up with a header file for my proposed interface and I would really appreciate any and all feedback on it.
Particularly, I'm interested in ideas for an appropriate replacement for using char *'s as the data buffers for reading and writing.
As a point of interest this interface is meant to be extremely simple. I don't intend to initially support ANYTHING except for basic creation and reading and writing.
Thanks! -- Geoff
Nothing is ever easy.
Hey all, So I'm officially finished with my independent study on named pipes, and I thought I'd post and let you all know that a working implementation exists. It's ugly, primitive and lacking most of the features one would actually want to use, but it exists :) The source is on github https://github.com/ezephyr/named-pipe. After I get back from a week-long camping trip, I'll be starting to work on reimplementing this as part of Boost.ASIO, which will be a much more useful end product I think. Thanks for the feedback and suggestions! Cheers, -- Geoff Nothing is ever easy.