https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4372
--- Comment #9 from Guy Harris <guy@xxxxxxxxxxxx> 2010-03-10 11:13:30 PST ---
> I guess that the enumeration is costly so they don't want to do it every time.
It's not "every time", it's just "every time people ask what interfaces there
are".
> Also since multiple clients may use winpcap at a given time, updating the list on the fly requires tricky synchronization logic.
If there's an API provided to provoke WinPcap to recheck for interfaces, that
would mean that multiple clients could call that API at a given time, so you'd
still need the synchronization logic.
> I asked them however to provide an API to refresh the list. For start it may even fail if there is an open winpcap client.
If that's how they handle the synchronization problem, then the WinPcap calls
to enumerate the interfaces could just call that routine and ignore its
failure. Again, that hides that detail inside WinPcap, rather than requiring
applications - Wireshark is not the only application that uses WinPcap - to be
changed to use that routine.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.