Wireshark-dev: Re: [Wireshark-dev] Structure of protocol tree
From: Gerald Combs <[email protected]>
Date: Wed, 15 Dec 2010 09:09:09 -0800
What are you talking about? It's Wednesday. Everyone knows that UTF8Strings have indefinite lengths on Wednesdays.

On Dec 15, 2010, at 8:50 AM, Jaap Keuter wrote:

> Hi,
> 
> "With the proper use of subtrees the structure of even the most complex
> protocols becomes clear."
> ... and then came ASN.1 ... ;)
> 
> Thanks,
> Jaap
> 
> On Wed, 15 Dec 2010 17:32:13 +0100, "news.gmane.com"
> <[email protected]> wrote:
>> "Jaap Keuter" <[email protected]> wrote in 
>> message news:[email protected]...
>>> Hi,
>>> 
>>> This 'colorize' is mainly intended to mark changeover into another
>>> protocol.
>>> Usually you see this at the top level (from the root), but occasionally
>>> when a protocol is encapsulated (some ITU protocols show this).
>>> As long as your 'structures' are at the top level, these could be
>>> considered valid use if they are truly independant, otherwise it's just
>>> poor style.
>> 
>> Well the protocol is designed as it is. And I think you agree that it would 
>> be an abuse to highlight structure starts similar (but not identically) as a 
>> protocol.
>> 
>> Does anybody see any other way to help the eyes to find the next structure 
>> in a complex packet structure?
>> 
>> --
>> Andy
>> 
> 
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <[email protected]>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>             mailto:[email protected]?subject=unsubscribe