As Jaap pointed out, the README is a great resource in understanding taps. The Wireshark User Manual also includes a page on taps (aka "Listener") (but it's sadly sparse and actually outdated).
What is resetting a tap?
listener.reset() is an interface function (or a callback) that Wireshark automatically calls as a notification to reset any state for the tap (e.g., counters). It's called on opening (and closing) a capture file or by the Refresh Button in Wireshark. If you don't maintain state, you don't need to implement this.
What is removing a tap?
listener.remove() unregisters the tap thereby ending any subsequent calls to listener.packet(), listener.reset(), and listener.draw(). Why call it? Think of this as turning off the light when you leave the room. It's an important step to conserve resources in Wireshark.
What information is lost when the tap is reset or removed?
Short answer: "none"
By "information", I assume you mean some kind of state variable. No information is maintained by the tap. State variables would have to be declared outside of the tap. Therefore, destroying the tap has no effect on the state.
When is the information lost when the reset and remove functions are called?
N/A (see previous answer)
What is the difference between these two functions?
See above
answered
02 Feb '12, 18:25
helloworld
2.6k●2●17●39
accept rate:
27%
Have you read README.tapping for some insights? It's C oriented, but talks about taps.