[andreas.sikkema@xxxxxxxxxxx]

> In summary I guess you could say I wrote the MGCP dissector as a plugin
> because it increases the isolation of the MGCP dissector from ethereal.
> I see this as a good thing.  I was always taught that your modules should
> be as weakly bound to each other as you can manage.  This is just a
> weakening of that bind.  Increased modularity is good.

I'd love to do this with the H.323 stuff, but because part of the protocl
is Q.931 based I can't.... Well, I could put my own Q.931 dissector in
the plug-in, but that's a road I don't want to follow.

If only you could call an Ethereal basic function which returns the address 
of the protocol dissector from a plugin, f.i.:
  dissector_q931 = get_dissector_address("Q.931");

But apart from that, I think I still would have problems linking the plugin....

-- 
Andreas Sikkema
andreas.sikkema@xxxxxxxxxxx