net: File method of Conn on Windows

[vyrus001]

I am writing something that requires access to the file descriptor of a socket created by net.Dial (which returns a net.conn) and then recast as net.TCPConn so that I can use net.TCPConn.File().Fd().

However, (as the error message says), "dup is not supported on windows". for my purposes, I don't "need" the dup() and would love to settle for just getting the raw file descriptor, but sadly the code within conn.File() appears as follows.

https://golang.org/src/net/net.go?s=5510:5555#L195

func (c *conn) File() (f *os.File, err error) { return c.fd.dup() }

Is there any way I could ask for an "if windows then just return c.fd" option? Hopefully this request isn't a waste of time, I am far from an expert on go.

[mikioh]

See #9503. We need a good compromise for both issues, and so need Windows experts.

[alexbrainman]

I don't think you can have "if windows then just return c.fd" option, because it is not what (*conn).File documented to do. Why do you need access to Windows socket handle?

Alex

[mattn]

Excuse me for discuss, because we want to pass socket handle into external process for listening. For example, to implement graceful server, we often use fork/exec model.

[vyrus001]

In my case, I am passing it to some c compiled with cgo for additional
functionality
On Apr 7, 2015 12:36 AM, "mattn" notifications@github.com wrote:

Excuse me for discuss, because we want to pass socket handle into external
process for listening. For example, to implement graceful server, we often
use fork/exec model.

—
Reply to this email directly or view it on GitHub
#10350 (comment).

[alexbrainman]

@vyrus001 there is no way to access original socket. If you need that functionality, you have to make copy of main Go repo and make whatever changes you want to net package.

@mattn I am not sure what you require, but have you tried implementing windows version of (*netFD).dup? Just use syscall.DuplicateHandle. Would that work for you?

Alex

[mattn]

@alexbrainman

https://msdn.microsoft.com/ja-jp/library/windows/desktop/ms724251%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

You should not use DuplicateHandle to duplicate handles to the following objects:

• I/O completion ports. No error is returned, but the duplicate handle cannot be used.
• Sockets. No error is returned, but the duplicate handle may not be recognized by Winsock at the target process. Also, using DuplicateHandle interferes with internal reference counting on the underlying object. To duplicate a socket handle, use the WSADuplicateSocket function.

[alexbrainman]

Fair enough. Use WSADuplicateSocket instead. Would that work for you?

Alex

[mattn]

Works fine. (But not enough to do that I want)

Look this: https://github.com/mattn/gospel/blob/master/example/echo-server.go

This is not possible to build currently. For building, it need https://codereview.appspot.com/177590043/

This is fork/exec model server. This can replace executable without stop server with SIGHUP. This package is passing socket handle into child process on windows.

[alexbrainman]

@mattn your old CL needs to be moved into Gerrit and made work on tip before we can discuss it.

Alex

[mattn]

https://go-review.googlesource.com/#/c/8683/