[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ethereal-dev
Subject:    Re: [ethereal-dev] [LEEDSNET] Error output & logginf whilst developing ethereal
From:       Florian Lohoff <flo () rfc822 ! org>
Date:       2000-03-25 6:31:58
[Download RAW message or body]

On Fri, Mar 24, 2000 at 12:18:14PM -0800, Guy Harris wrote:
> Snoop (and maybe some other sniffers) tag replies with "This is a
> response to frame XXX".
> 
> "This is a response to frame XXX" could probably be added to the
> protocol tree at the appropriate point (in the subtree for the protocol
> that recognizes it as such); with some additional work, we could
> probably add "The response to this is in frame XXX" as well.
> 
> We could also then reserve a value for this property meaning "this is a
> {request,response} but we don't know {which frame is the response,which
> frame it's a response to}".
> 
> Then finding all requests and replies would involve searching for frames
> with one of those properties; we could also then provide a menu item to
> find the request for/reply to a given packet.

I though of just adding filter functionality to those 
informations needed to identify the response/request and using the filter
functionality not to limit the displayed packets but to jump to the requested
packet.

Flo
-- 
Florian Lohoff		flo@rfc822.org		      	+49-5241-470566
"Technology is a constant battle between manufacturers producing bigger and
more idiot-proof systems and nature producing bigger and better idiots."

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic