[Wireshark-dev] Which takes precedence - plug-ins or built-in dissectors?
Mea culpa if this is a FAQ but I couldn't find reference to this anywhere. 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? Cheers, Bryan ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
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@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Which takes precedence - plug-ins or built-in dissectors?
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Which takes precedence - plug-ins or built-in dissectors?
On Mar 28, 2007, at 2:28 PM, Bryan Miller wrote: > 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. So is this an extension to an existing protocol, or a completely new protocol? (A new ONC RPC-based protocol or a new DCE RPC-based protocol is a new protocol, not an extension to an existing protocol.) If it's a completely new protocol, there's no dissector already statically linked into Wireshark. If it's an extension to an existing protocol, you'll have to modify the existing dissector and build a private version of Wireshark for internal use. (Anybody outside your organization to whom you give the modified version can ask for the source, and you have to provide it to them, and they can then give the source away to anybody they want.) ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
