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

net: UDPConn.WriteTo w/ connection-oriented mode socket fails on BSD variants #2773

Closed
mikioh opened this issue Jan 24, 2012 · 4 comments
Closed
Milestone

Comments

@mikioh
Copy link
Contributor

mikioh commented Jan 24, 2012

What steps will reproduce the problem?
1. run attached program
2.
3.

What is the expected output? What do you see instead?
2012/01/24 23:46:05 WriteTo with CO socket: darwin write udp 8.8.8.8:53: socket is
already connected

Perhaps it might be better WriteTo w/ connection-oriented mode 
UDPConn can ignore or override pre-specified destination address 
by connect like Linux.

But I'm really not sure whether it should be.

Please use labels and text to provide additional information.

Attachments:

  1. udpconn.go (793 bytes)
@mikioh
Copy link
Contributor Author

mikioh commented Jan 24, 2012

Comment 1:

the result of toy experiment:
Darwin:
2012/01/24 23:46:05 WriteTo with CO socket: darwin write udp 8.8.8.8:53: socket is
already connected
2012/01/24 23:46:05 Write with CL socket: darwin write udp: destination address required
FreeBSD:
2012/01/24 23:46:51 WriteTo with CO socket: freebsd write udp 8.8.8.8:53: socket is
already connected
2012/01/24 23:46:51 Write with CL socket: freebsd write udp: destination address required
Linux:
2012/01/24 23:46:11 Write with CL socket: linux write udp: destination address required

@mikioh
Copy link
Contributor Author

mikioh commented Jan 24, 2012

Comment 2:

http://golang.org/cl/5571056

@rsc
Copy link
Contributor

rsc commented Jan 25, 2012

Comment 3:

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

@mikioh
Copy link
Contributor Author

mikioh commented Jan 26, 2012

Comment 4:

This issue was closed by revision 974fa75.

Status changed to Fixed.

@rsc rsc added this to the Go1 milestone Apr 10, 2015
@rsc rsc removed the priority-go1 label Apr 10, 2015
@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
Development

No branches or pull requests

3 participants