Guy, I am in agreement and that is what I anticipate doing with the bulk of my
work. I this particular case the protocol is proprietary and will likely not
become public until 2008.
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: Wednesday, March 28, 2007 10:32 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Which takes precedence - plug-ins or built-in
dissectors?
Bryan Miller wrote:
> What happens if I add a plug-in for a dissector that already is
> statically linked into Wireshark? Does the plug-in take precedence or
> will there be a conflict?
There is no guarantee of any particular outcome. It depends on the
mechanism the dissectors use to register themselves, and the way those
mechanisms happen to be implemented in any particular version of Wireshark.
If you have improvements for a dissector, you should replace that
dissector directly, and send us the improvements so we can put them into
the main Wireshark release. _______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev