Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

os: named pipes support on Windows #3599

Closed
nsf opened this issue May 8, 2012 · 9 comments
Closed

os: named pipes support on Windows #3599

nsf opened this issue May 8, 2012 · 9 comments

Comments

@nsf
Copy link

@nsf nsf commented May 8, 2012

Just want to drop a note here. Sorry for me not willing to implement it myself. Consider
it as a feature request.

On *nix we have unix sockets - a standard way of doing IPC (interprocess communication).
On windows we can use TCP sockets for doing the IPC, but a natural way of doing so
according to this page
(http://msdn.microsoft.com/en-us/library/windows/desktop/aa365574(v=vs.85).aspx) is
named pipes. Very close analogy to unix sockets. Providing the appropriate functions in
the syscall package as well as integrating them with "net" package sounds like
a good idea to me.
@alexbrainman

This comment has been minimized.

Copy link
Member

@alexbrainman alexbrainman commented May 9, 2012

Comment 1:

Just my 2 cents. I have used named pipes on Windows in the past. It is useful facility
at times, because they look like files, so it is easy to use them from different
languages. I am not sure if they belong in "standard" library. People who need them
should create go gettable package.
Alex
@rsc

This comment has been minimized.

Copy link
Contributor

@rsc rsc commented Sep 12, 2012

Comment 2:

Labels changed: added priority-later, removed priority-triage.

Status changed to Accepted.

@natefinch

This comment has been minimized.

Copy link
Contributor

@natefinch natefinch commented May 21, 2013

Comment 3:

I made an implementation here:
https://github.com/natefinch/npipe
It should be considered beta-quality software, as it has not been put to rigorous use
yet. I encourage pull requests.
@rsc

This comment has been minimized.

Copy link
Contributor

@rsc rsc commented Nov 27, 2013

Comment 4:

Labels changed: added go1.3maybe.

@dsymonds

This comment has been minimized.

Copy link
Member

@dsymonds dsymonds commented Dec 4, 2013

Comment 5:

Labels changed: added os-windows, feature, removed priority-later.

@rsc

This comment has been minimized.

Copy link
Contributor

@rsc rsc commented Dec 4, 2013

Comment 6:

Labels changed: added release-none, removed go1.3maybe.

@rsc

This comment has been minimized.

Copy link
Contributor

@rsc rsc commented Dec 4, 2013

Comment 7:

Labels changed: added repo-main.

@kardianos

This comment has been minimized.

Copy link
Contributor

@kardianos kardianos commented Aug 19, 2014

Comment 8:

No action has happened on this. Would a CL be desirable for the net or sub-repo net
package? I have used nate's npipe package for quite some time now. It works well and is
very robust in my experience.
As this is a Windows only feature, I'm doubtful it belongs in the standard repo. Perhaps
in net sub-repo at best? I for one am fine with it as a go-gettable package, though I'd
hate to see it disappear if nate did.
I would vote to just recognize the status quo and close the issue. Get this feature
from: gopkg.in/natefinch/npipe.v2
.
@alexbrainman

This comment has been minimized.

Copy link
Member

@alexbrainman alexbrainman commented Aug 20, 2014

Comment 9:

SGTM
nate's package looks nice, and anyone can "go get" it. Closing this issue unless someone
objects.
Alex

Status changed to WontFix.

@nsf nsf added wontfix labels Aug 20, 2014
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants
You can’t perform that action at this time.