[Guy Harris <guy@xxxxxxxxxx>]

On Thu, Feb 06, 2003 at 02:45:20PM -0500, Jason House wrote:
> > On Thu, Feb 06, 2003 at 09:55:52AM -0500, Jason House wrote:
> > > The best answers are sometimes by example.
> > > You have two approaches:
> > > One way is you can do the approach of tap-iostat.c
> 
> Oops, I meant to say tap-protocolstat.c.   sorry :(

	hostname$ cd src/cmd/ethereal
	hostname$ find . -name tap-protocolstat.c -print
	hostname$ 

So where is "tap-protocolstat.c"?

Or did you mean "tap-protocolinfo.c"?

> > >    The only trick there becomes adding what you want to the filter
> > > string...
> 
> ... causing edt->tree to cache the result for the particular field(s) of
> interest... and then simply calling proto_get_finfo_ptr_array (see
> protocolinfo_packet).

It sounds as if that's what you meant.

> That's only necessary if Miha needs to preserve the structure of the tree or
> not.
> Maybe I misunderstood his request... I was under the impression that he
> simply wanted to read a specific field of a packet.

So was I, but I didn't remember "proto_get_finfo_ptr_array()".