Having only glanced at the source code recently I'm not sure how well
this fits into the framework but here is my thought.
Instead of having all these defines and structures that describe a
particular protocol how about
something that could be read in at runtime. I was first thinking text
files, possibly including
a BNF formula representation but that might be be messy. Then I
thought about XML.
If a particular protocol was described using XML then it could be
enhanced or new protocols
might even be able to be added simply by creating the appropriate
description in it of XML.
I was actually thinking about this in the context of building a USB
protocol analyzer but
Ethereal came to mind and I thought it might be a very useful addition
to ethereal for network packets.
I guess the question is how stateful are the protocol modules in
Ethereal, it seems that
if they could be described by a BNF language then they would work well
in XML.
So maybe someone with more experience with Ethereal can tell me if this
is an idiotic idea or
if there is some merit here?
I looked through the archives a bit and didn't see any discussion on
this so forgive me if I am beating
a dead horse.
Thanks,
Doug
remove the _NOSPAM if replying directly
mcdorman_NOSPAM@xxxxxxx
