Ethereal-dev: Re: [Ethereal-dev] New FT type

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: Gilbert Ramirez <gram@xxxxxxxxxx>
Date: Thu, 25 Jan 2001 12:08:57 -0600
On Wed, 24 Jan 2001 16:33:19 -0600
Frank Singleton <frank.singleton@xxxxxxxxxxxx> wrote:

> Will your changes make it into ethereal anytime soon ?
> It would be nice for me. Otherwise I am forced to use
> my previous strategy of adding lots of  things to packet-giop.
> 
> Comments ??
> 
> Cheers / Frank..
> 

Probably not for another 2 weeks.
After that we can think about doing other things with FT types, like
coalescing all the integer types into a FT_UINT and FT_INT (or maybe
just one) and have the bit-width be a *property* of the particular
header_field_info struct. Maybe another property would be the
particular encoding in the packet, so that your FT_CDR_LONG
might actually be an FT_UINT with a particular encoding.
(I don't know what an FT_CDR_LONG is, so this may not be
an accurate dream).

The 3 FT string types, for example, are all strings, but with
different encodings. Perhaps the encodings should go in the
header_field_info struct instead of the type itself. I don't know
yet; it's just some idle thoughts.

--gilbert