Hi all,
When looking at why
conversations have been included in Ethereal development, I assume that their
sole intention is to ease packet dissection. The conversation logic does not
intend to deal with protocol-layer sessions... yet?
Wouldn't it be useful to
have functions like conversation_add_session(), conversation_get_session(),
and same for session data storage and retrieval?
BTW I noticed that conversation
selection happens by computing a hash on the address, not on the address itself.
Although a private exact match function exists, but it is only called when a new
capture file is loaded.
Regards,
Olivier
