Kalk, Christian wrote:
Suggestion:
Introduce a feature called the conversation ID.
You could then filter on multiple conversation IDs (will work like
follow TCP-conversation, but instead of using TCP ports and IPs it will
work more natively through the conversation number -> conversation == 3
|| conversation == 9) and you could show it as a new column on the UI.
I've thought about exactly the same thing before.
The problem is (and I'm probably not alone with this): The applications
I work with uses several layers, which TCP is only one of and I'm
usually interested of the conversations on other layers as well.
You could think about such a "conversation" for UDP and a lot of other
(higher level) protocols as well.
I would like to have a more general mechanism, not only for TCP, but
after thinking about it for a while, I couldn't find a really good way
to display this in a convenient and intuitive way :-(
Benefit:
- Upgrade the "follow TCP stream" from using Sockets to conversation ID
- with the new column, directly see when clients open sessions, ask one
thing, close the session and do that 20 times by raising conversation
ID.
You like it? How to proceed?
You may add this to the WishList, so at least it won't get lost for now.
Regards, ULFL
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
