Ethereal-dev: Re: [Ethereal-dev] More and more need to access dissection routines from all ove
Richard,
regarding the COL_INFO stuff I would like to say that protocols
running over SCTP have to deal with the fact that multiple
upper layer protocol data can be part of one SCTP packet. Since the
dissector and most of the upper layers are written by myself it
was easy to only use append instead of set for the COL_INFO stuff.
But it would be helpful is this could be handled 'automatically'.
Maybe a protocol can set the COL_INFO stuff in a state: ONLY_APPEND
where even set calls are modified to APPEND, or DONT_MODIFY where
append and set calls are simply ignored.
Best regards
Michael
On Tuesday, Oct 1, 2002, at 23:39 Europe/Berlin, Richard Sharpe wrote:
There are more and more places where we are starting to need dissector
routines in one dissector for a structure that is known about in
another
dissector. For example, in the Windows world, they seem to place a lot
of
their existing structures on the wire as blobs. Security descriptors
seem
to turn up all over the place.
Do we need a[nother] mechanism for registering and retrieving such
dissectors?
Also, we might need some new coding guidelines because there are cases
where some dissectors could almost be called from other dissectors,
except
that they should avoid modifying the COL_INFO column, for example.
Regards
-----
Richard Sharpe, rsharpe@xxxxxxxxxx, rsharpe@xxxxxxxxx,
sharpe@xxxxxxxxxxxx
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
