Wireshark · Ethereal-dev: Fwd: [Ethereal-dev] 0.10.8 soon?( Mate)

[LEGO <luis.ontanon@xxxxxxxxx>]

> epan/plugins.c
I'll see what I can do.

> It doesn't matter, if Mate is a plugin or a part of libethereal. We have
> to add some code to arrange that Mate is initialized at last. I
> personally would prefer to keep it as a plugin for some time. This
> dissector is different to all other dissectors and needs some testing.

I couldn't agree more. I think it is worth to leave it  as a plugin
for a while.
And, I love the "compile in 3 seconds" thing :-)

> BTW, what is the status of Mate's compability with tethereal?

Mate uses the tap to fetch data from the tree, and creates the tree
fetching the data from a hash when called as a dissector.

The reason it works on ethereal and does not work on tethereal is
simple, is the same reason why filtering on mates fields doesn't work
at the very first run. The tap runs after the dissector has been
called, so there's no data yet to build a tree.

I've tried in the past to populate the tree from the tap, but it did
not work (it just crashed). That's, I believe, because the tree has
been already pruned when the tap runs.

Once I used to "prime" the tree in file.c and then to call mate from
packet.c after frame was called but that didn't work for that neither.

I'll keep working on mate itself for a while. I have still two
features to add, mergeing gogs with common keys and spawning
implicitly started gops from gogs. There are still several issues
regarding gogs to be solved. And who knows how many bugs I do not know
about still to fix.

Once I get there I'll be back to "fitting mate well into ethereal".

Regards,
Luis


-- 
We can classify people in 10 categories:
- those who understand binary
- and those who don't