On Tue, Jul 16, 2002 at 12:15:33PM -0700, Fulvio Risso wrote:
> They are already implemented.
> The fact is that we believe the actual API is a bit confusing, so in our
> docs we suggest not to use these calls.
> Instead, we defined a pcap_read_ex() which reads a packet at a time
> (like pcap_next() ), it is non blocking,
In the current WinPcap 3.0 alpha source, both "pcap_read_ex()" and
"pcap_read()" call "PacketReceivePacket()" with the same arguments, so
it appears that either
1) both "pcap_read_ex()" and "pcap_read()" are always
non-blocking, in which case "pcap_dispatch()" and
"pcap_loop()" are non-blocking on Windows (which is an API
change that would cause programs unaware of the change to
spin in a CPU-consuming loop while waiting for packets)
or
2) both "pcap_read_ex()" and "pcap_read()" are blocking unless
non-blocking mode has been turned on.
-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
