-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
Rename readmsg to recvmsg #4684
Conversation
* Fix inconsistency of naming w.r.t. MRI.
This bit of functionality is critical for RubyDNS which.. uses UDP |
I have to admit I'm not familiar with the "recv" set of socket functions. What we have implemented today is largely just using "read" and simulating other parameters to "recv" and "recvfrom". The main challenge is mimicking these lower-level socket APIs on the JVM, where we have only high-level APIs that hide access to the actual file descriptors or the lower-level operations. We've managed to fake it well enough for the standard socket types, but when you get to more unusual sockets we still struggle a bit. So, to clarify a few things.
Supporting the general case of recv on all types of sockets may not be doable with Java's APIs, but a specific goal of getting enough of Socket#recvmsg to work for DNS should be possible. |
Java has
You will normally use UDP sockets can be connected.
That would be great. |
Bump. |
So, I assume the API you need to use in Java is |
Is there some reason why we can't merge this? |
Bump :) |
Sorry, this slipped through for too long. Marking for 9.2.1. |
That would be awesome. |
Could this be updated to the current code base? Thank you! |
Uh, I didn't even look at the code originally, but it seems like it's not even implemented. At least we can fix the name.. but can we fix the implementation too?