Guy,
my previous reply was sent before I saw your last message.
There IS a chance more than one instance of the Object owning the
native methods would be created IF there would be need to sniff at
several network interfaces simultaneously; in which case there would
be a single instance of the class for each network interface to be
sniffed.
Could this raise the issues you mention above?
2014-02-13 13:11 GMT-05:00, Daniel H. Bahr <dhb...@gmail.com>:
> I see what you mean, but the native startSniffing method is invoked
> from a nested inner Thread. That is:
>
> Java Main Thread {
> do stuff...
> Nested Outer Thread {
> do more stuff...
> Nested Inner Thread {
> startSniffing here...
> }
> }
> }
>
> 2014-02-13 12:29 GMT-05:00, Michael Richardson <m...@sandelman.ca>:
>>
>> The other thought I have is that java is heavily threaded, while libpcap
>> is
>> not thread safe. pcap_loop() is going to block.
>> I see that your jni variable is a global... I wonder about that.
>>
>> --
>> ] Never tell me the odds! | ipv6 mesh
>> networks
>> [
>> ] Michael Richardson, Sandelman Software Works | network
>> architect
>> [
>> ] m...@sandelman.ca http://www.sandelman.ca/ | ruby on rails
>> [
>>
>>
>
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
