Ethereal-dev: RE: [ethereal-dev] Library plans

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

Date: Thu, 21 Sep 2000 15:29:14 -0500

Yes, that does fit into my plans. I too would like to emulate apache in that
regard.

Yes, I do plan to support heuristic-based dissectors, since they're absolutely
required for the functioning of some dissectors.

--gilbert

Jeff Foster <jfoste@xxxxxxxxxxxx> on 09/21/2000 03:20:18 PM

To:   "'Gilbert Ramirez'" <gram@xxxxxxxxxx>
cc:   ethereal-dev@xxxxxxxx (bcc: Gilbert Ramirez/Tivoli Systems)
Subject:  RE: [ethereal-dev] Library plans





per gilbert:
> > >
> > > I'd like to modify the plugin API to use dissector tables and get rid
of the
> > > display-filter-based plugin API.
> >
> > What does it mean / imply ?
>
> What I mean is to use this method of registering a plugin:
>
> old_dissector_add("tcp.port", TCP_PORT_GRYPHON, dissect_gryphon);
>
> instead of:
>
> DLLEXPORT const gchar filter_string[] = "tcp.port == 7000";
>
> Of course, this will require some sort of GUI to configure.

Do you plan to support to the heuristic base dissectors?

I would like to see a long term goal of making all dissectors dynamically
loadable, kind of the apache modules point of view.  I don't know if this
fits into your plans, just something to think about.

Jeff Foster
jfoste@xxxxxxxxxxxx