[Protocol-dev] RFC: oob/urgent/except handling

[Protocol-dev] RFC: oob/urgent/except handling

Tom Marshall tmarshall at helixcommunity.org
Thu Oct 14 12:00:36 PDT 2004


The net API allows the user to select the EXCEPT event.  But none of our
code actually does it and, at least in the server, the EXCEPT event is not
wired into the select/poll loop.  As a result, TCP sockets stall when OOB
data is sent.

Note that TCP OOB data is not reliable (portable) between OSes.  Even today,
some TCP/IP stacks implement RFC 793 and some implement the correction in
RFC 1122 section 4.2.2.4.

What should be done about this situation?  Is there any reason that we
shouldn't just remove HX_SOCK_EVENT_EXCEPT from hxnet.h and set the
SO_OOBINLINE option on all sockets?

-- 
To err is human; to really screw things up requires the root password.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.helixcommunity.org/pipermail/protocol-dev/attachments/20041014/e5f16ec9/attachment.bin


More information about the Protocol-dev mailing list
 

Site Map   |   Terms of Use   |   Privacy Policy   |   Contact Us

Copyright © 1995-2007 RealNetworks, Inc. All rights reserved. RealNetworks and Helix are trademarks of RealNetworks.
All other trademarks or registered trademarks are the property of their respective holders.