Hi!
I agree we should have a framework for decoding VoIP and other
conversations, where adding a new protocol should be trivial. My opinion
is that in this case we shouldn't fix the column with predefined names
and values like IP, IP:port, status, etc... because not all use the same
parameters (f.e. faststart is H323 specific). So maybe we should have
some general routines similar to those in h323_conversations_dlg.c (plus
some fromh323_conversations.c) and could be the same for all protocols.
This routines would be able to draw the dialog window, register the
taps, specify the filter and other general stuff. They could be called
from the menu list and depending on which protocol was choosed
(Menu->Conversations->H323, Menu->Conversations->SIP,
Menu->Conversations->...) with the parameters required to do the actual
decoding: title, number of columns, columns names, protocol used, ...
With this approach you can add any new protocol but you have to write
all the tap routines. The question is, is it possible to write also the
tap routines in a general way, without getting to much limitations?
Regards, Miha
--
Miha Jemec <m.jemec@xxxxxxxxxxx>