To get that info you need raw socket access. You can do it I suppose but you are getting into a fairly deep area. See this for some idea of how easy it isn't. You will note that even WinSock support for it is not a given. It depends on which flavour you are running.

Probably the easiest workaround is to accept that the socket will block on win32. To get a non-blocking effect run two processes. The blocking UDP message acceptor process block waiting for data, as you have now. When it has something to say it says it. The other process listens effectively via a non blocking read. Ugly but it would work and is probably the easiest implementation.

cheers

tachyon

In reply to Re^5: IO::Socket::INET -- Jettero verses non-blocking in windows by tachyon
in thread IO::Socket::INET -- jettero verses non-blocking in windows by jettero

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.