structure to the "packet_info" structure; only stuff that's permanently
stored with each frame should be in the "frame_data" structure, and the
"column_info" structure is not guaranteed to hold the column values for
that frame at all times - it was only in the "frame_data" structure so
that it could be passed to dissectors, and, as all dissectors are now
passed a pointer to a "packet_info" structure, it could just as well be
put in the "packet_info" structure.
That saves memory, by shrinking the "frame_data" structure (there's one
of those per frame), and also lets us clean up the code a bit.
svn path=/trunk/; revision=4370
take a dissector handle as an argument, rather than a pointer to a
dissector function and a protocol ID. Associate dissector handles with
dissector table entries.
svn path=/trunk/; revision=4308
of protocol-id-plus-datum pairs, so that multiple protocols can attach
information to the same conversation.
Dissectors that attach information to a conversation should not assume
that if they find a conversation it has one of its data attached to it;
the conversation might've been created by another dissector.
svn path=/trunk/; revision=3901
FT_NONE, not FT_STRING, as they have no value assigned to them.
Don't use "hf_ssl_handshake_certificate" both for the collection of all
certificates and for individual certificates, add a new
"hf_ssl_handshake_certificates" FT_NONE field for the collection of all
certificates, as is done for other collections.
Properly pluralize the "N specs" in the item for the collection of
cipher specs.
Properly label the second "ssl.record" as "SSLv2 record data", not
"Length of SSLv2 record data".
Fix a typo in the field name of the field for the length of the
collection of certificates.
svn path=/trunk/; revision=3725
Opaque fields should be FT_BYTES, not FT_STRING; FT_STRING is for text
strings.
Don't supply a null value when putting an FT_BYTES field into the tree;
supply a pointer to the actual bytes.
For items with subtrees, use "proto_tree_add_text()" if the actual value
of all the stuff under the subtree, treated as a big array of bytes,
isn't interesting (e.g., if the individual items are put into the
protocol tree). Also, make the items with subtrees refer to the same
data as all the items under them.
svn path=/trunk/; revision=3724
