Ethereal-dev: Re: [Ethereal-dev] moving from plugin to buildin

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Richard van der Hoff <[email protected]>
Date: Tue, 27 Jul 2004 18:48:50 +0100
On Tue, Jul 20, 2004 at 11:30:09PM +0200, Erwin Rol wrote:
> On Tue, 2004-07-20 at 23:08, Lars Roland wrote:
> > Erwin Rol wrote:
> > > Hey all,
> > > 
> > > I would like to make the plugins that i maintain (acn, artnet, enttec,
> > > rdm and  later rtnet) into buildin dissectors. The reason is that i
> > > would like to add some things based on the TAP interface and as i
> > > understood it thats not really doable in a plugin. Also i don't see any
> > > main advantage anymore in having plugins instead of buildins. 
> > > 
> > The mgcp dissector plugin uses the tap interface.
> > But the code for the mgcp taps is linked statically into (t)ethereal 
> > even with libethereal.dll.
> 
> This is what i mean , it gets a bit of a mix between buildin and plugin,
> and now we have SVN i thought it would be better to make it all buildin.

Isn't the main advantage of making your dissector a plugin that you
don't have to wait half an hour every time you make a tiny change, while
the whole of libethereal is relinked?

I would have thought that plugins are *preferable* where possible.

Having said that, I've never tried using the TAP interface, so I'm happy
to believe that in this case you need to make your dissector built-in.

-- 
Richard van der Hoff <[email protected]>
Systems Analyst
Tel: +44 (0) 845 666 7778
http://www.mxtelecom.com