Ethereal-dev: Re: SV: [Ethereal-dev] What's changed with operational dissection?

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

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Jaap Keuter <jaap.keuter@xxxxxxxxx>
Date: Sat, 29 Oct 2005 14:56:42 +0200 (CEST)
So, this means that using any of the 'advanced' features (like coloring)
causes ethereal to be less efficient for these protocols. Good thing to
know :-)

Thanx,
Jaap


On Sat, 29 Oct 2005, Ulf Lamping wrote:

> Jaap Keuter wrote:
>
> >Still the question below remains. Why is the dissector always called with
> >a tree != NULL parameter?
> >
> >
> I'm really not an expert on this, but as far as I remember:
>
> Any time fields are probably used (filtering, coloring, ...) the tree
> will be != NULL.
>
> Some things don't need the tree (so it will be tree == NULL) e.g. for
> the cf_retap_packets() call.
>
> Regards, ULFL
>