Yes. For example one might put in a post dissection point into the
api so that I could register a function with ethereal that gets called
after a packet is dissected. Then I could add a plugin that would
query each dissected packet to gather statistics. Naturally because
ethereal in it's current form redissects packets quite a lot
some thought should go into the correct way to handle such an insertion
point ( and please note I've not looked at the code yet to get a
really strong idea of what would be involved ). So if I wanted
to write a nice gui statistics tool that plugged into ethereal
I could use this insertion point as a base. The idea is to
keep the plugin guys out of the core as much as possible
by making the functionality they are likely to need
available to them. ( No offense to the plugin guys, I suspect you would
LIKE to stay out of the core as much as you can get away with).
Just a thought.
Ed
On Sat, 14 Jul 2001, Guy Harris wrote:
> On Sat, Jul 14, 2001 at 02:03:51PM -0400, Ed Warnicke wrote:
> > 5) Put a plugin architecture into ethereal and associated tools
> > ( not libethereal, in my view dissectors should plug into
> > libethereal, most tools probably shouldn't).
>
> "A plugin architecture" presumably includes the places where sockets are
> put into which stuff is to be plugged in, right?
>
