Wireshark mailing list archives

Re: Structure of protocol tree


From: Jaap Keuter <jaap.keuter () xs4all nl>
Date: Wed, 15 Dec 2010 17:50:04 +0100

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"
<AndreasSander1 () gmx net> wrote:
"Jaap Keuter" <jaap.keuter () xs4all nl> wrote in 
message news:75883c052eaf82074dac3aef04d29e94 () xs4all nl...
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 <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe


Current thread: