Message9510

Author zyasoft
Recipients gary.aviv, zyasoft
Date 2015-02-10.17:57:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1423591020.72.0.904117681997.issue2267@psf.upfronthosting.co.za>
In-reply-to
Content
As of 2.7.0 trunk, socket.recv does support the second parameter for flags, but it is quietly ignored.

It's an interesting exercise to match the standard Unix flags (http://linux.die.net/man/2/recv) and similar Windows flags against what we can do with Netty 4. I suppose something like socket.MSG_WAITALL can be implemented, but it's worth pointing out that this flag is not available on Windows. In general, in socket-reboot we have tried to do the intersection of socket support for Windows and Unix systems, because at the end of the day we are just simulating C socket semantics on top of Netty. See my design doc - https://github.com/jimbaker/socket-reboot
History
Date User Action Args
2015-02-10 17:57:00zyasoftsetmessageid: <1423591020.72.0.904117681997.issue2267@psf.upfronthosting.co.za>
2015-02-10 17:57:00zyasoftsetrecipients: + zyasoft, gary.aviv
2015-02-10 17:57:00zyasoftlinkissue2267 messages
2015-02-10 17:57:00zyasoftcreate