[Bug 32328] Many .NET and Silverlight applications require SIO_ADDRESS_LIST_CHANGE for interface change notifications

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=32328

--- Comment #27 from Austin English <austinenglish at gmail.com> ---
(In reply to Erich Hoover from comment #25)
> (In reply to Anastasius Focht from comment #24)
> > ...
> > --- quote ---
> > ...
> > Alternatively, if the SIO_ADDRESS_LIST_CHANGE IOCTL is issued on a
> > nonblocking socket and without overlapped parameters (lpOverlapped and
> > lpCompletionRoutine are set to NULL), it will complete immediately with
> > error WSAEWOULDBLOCK.
> > The Windows Sockets SPI client can then wait for address list change events
> > through a call to WSPEventSelect or WSPAsyncSelect with the
> > FD_ADDRESS_LIST_CHANGE bit set in the network event bitmask.
> > --- quote ---
> > 
> > I've already tested a fix, taking this into account (makes all of them to
> > work).
> 
> The applications I'm testing with don't have this behavior.  Does your test
> app need FD_ADDRESS_LIST_CHANGE or does it just need to return
> WSAEWOULDBLOCK?
> 
> Also... Woo-hoo! I'm really glad to finally get this in :)

If it works for your application, I'd say this bug should be marked fixed and a
new one opened for the remaining applications.

I don't feel strongly about it though, up to you.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.