comment on

This solution works admirably !

After setting the ioctl() command you're suggesting on my socket, I'm reading from it using sysread(), which behaves in a non-blocking way, returning the amount of bytes it has actually read. This overall works much faster than my looping approach, especially for longer messages.

Although this is probably off-topic, it's curious how the "magic value" of 0x8004667E is created. The "macro" for non-blocking IO in ioctl() is FIONBIO, and its calculation is done thus:

IOC_IN = 0x80000000h; 
FIONBIO = IOC_IN + 4 * 65536 + ORD ('f') * 256 + 126;
[download]

I wonder what is the rationale behind this ? Can someone explain how these things work ? Is it portable to just plunge the magic value in my code ?

In reply to Re^2: Non-blocking socket read on Windows by spurperl
in thread Non-blocking socket read on Windows by spurperl

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


We don't bite newbies here... much
	PerlMonks