Guy Harris wrote:
>
> > Any thoughts on whether a dissector (say, ISUP) should be able to know
> > the preferences settings of another dissector (say, MTP3)? There
> > doesn't seem to be any mechanism (short of making the preference
> > variable in MTP3 non-static and extern'ing it from ISUP, which I imagine
> > won't fly)
>
> It'll fly technically; is the "won't fly" concern that it may not be
> obvious to the user that an MTP3 option is the way to control the
> behavior of other protocols?
Actually, I just figured someone would come hunt me down for putting a
non-static variable in a dissector and referencing it from another
dissector. ;)
If it's okay (approved) to do it this way, it's probably the easist and
clearest way...
> If so, another option might be to use "prefs_register_module()" to
> create a preferences module with a name that's *not* the name of a
> particular protocol, register preferences under that, and make the
> variables controlled by those preferences global.
begin:vcard
n:Morriss;Jeff
tel;fax:+1-856-222-9947
tel;work:+1-856-787-2824
x-mozilla-html:FALSE
url:http://www.ulticom.com
org:Ulticom, Inc.;Customer Support
version:2.1
email;internet:jeff.morriss@xxxxxxxxxxx
title:Product Support Engineer
adr;quoted-printable:;;Ulticom, Inc.=0D=0A1020 Briggs Rd.=0D=0A;Mount Laurel;NJ;08054;USA
fn:Jeff Morriss
end:vcard