Ethereal-dev: Re: [Ethereal-dev] Advice on how to make a protocol grapher...

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: "Ronnie Sahlberg" <ronnie_sahlberg@xxxxxxxxxxxxxx>
Date: Tue, 27 May 2003 07:39:18 +1000
----- Original Message -----
From: "Jason House"
Sent: Tuesday, May 27, 2003 1:29 AM
Subject: Re: [Ethereal-dev] Advice on how to make a protocol grapher...


> Yes, that's what I was referring to.  In the ideal world, even one step
> further... Allowing for a rescan of the packet list even before the
> original one finished (since it never truly does in real-time
> updates)... ie. if io,stat GUI is used, and a new display is chosen, the
> display thread will stop parsing new packets, and go back and rescan old
> ones, and then continue on with new and queued packets.

I belive the taps already do this.
Open a tap listener window, load a capture, it updates every 3 seconds while
loading the capture.
Load a new capture, it will reset and start reupdating with the new data.
Start capturing live, the tap window will reset again and start updating its
window once every three seconds again.

> That is a good point.  Maybe there could be another checkbox for "Update
> taps in real time"... where there is no packet list GUI activity at
> all... and thus require a redisection of the packet list when the
> capture is stopped.

I belive the tap system already do this.