Add tables of "conversation" dissectors, which are associated with
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Tue, 9 Jan 2001 05:53:21 +0000 (05:53 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Tue, 9 Jan 2001 05:53:21 +0000 (05:53 +0000)
commita1f75fe99c63add12c6dca8d8c0bc31435568dfa
tree778736267614d5d1e7675f7357591bfc269be910
parentbc940e5213a098215671d9b488b48f5e311fbf3c
Add tables of "conversation" dissectors, which are associated with
particular protocols, and which keep track of all dissectors that could
be associated with conversations using those particular protocols - for
example, the RTP and RTCP dissectors could be assigned to UDP
conversations.

This is for future use with UI features allowing the dissector for a
given conversation to be set from the UI, to allow

1) conversations between two ports, both of which have
   dissectors associated with them, that have been given to the
   wrong dissector to be given to the right dissector;

2) conversations between two ports, neither of which have
   dissectors associated with them, to be given to a dissector
   (RTP and RTCP, for example, typically run on random ports,
   and if you don't have, in a capture, traffic that would say
   "OK, traffic between these two hosts and ports will be RTP
   traffic", you may have to tell Ethereal explicitly what
   protocol the conversation is).

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@2848 f5534014-38df-0310-8fa8-9805f1628bb7
epan/packet.c
epan/packet.h
packet-rtcp.c
packet-rtp.c
packet-tcp.c
packet-udp.c