Hi,
Come on over to Wireshark at www.wireshark.org. That is were the
developers are these days.
Thanx,
Jaap
On Thu, 29 Jun 2006, Kalk, Christian wrote:
> Hi.
>
> The wishlist said to check the dev-list before putting a wish up. So
> here is the email, there is the wish:
>
> Example-scenario:
> You have a tracefile with many protocols, filter down on a single one.
> You see different requests and responses between two entities, but you
> do not know, if all the packets are exchanged in the same TCP-session,
> because you usually do not see the TCP-3wh because you filtered just on
> the protocol frames.
>
> 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.
>
> 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?
> Please comment!
>
> Cheers!
> Chris :)
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
>
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
