Wireshark-bugs: [Wireshark-bugs] [Bug 5109] Moving backwards in compressed captures is extremely
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5109
--- Comment #4 from Guy Harris <guy@xxxxxxxxxxxx> 2010-08-12 18:27:08 PDT ---
It appears that both find next/previous time reference and find next/previous
marked frame have always used the generic find next/previous matching a filter
code. If we were to bypass that, we'd want the find code for time reference
and marked frames to use as similar a code path as possible to find
next/previous matching, so we'd probably want most of that code path to be
shared by those, perhaps with a callback to do the "this is the frame you want"
check.
Another possibility would be to have some filter predicates not bother to read
or dissect the frame, and use those predicates for "time reference frame" and
"marked frame"; that would also let you filter for marked/unmarked frames and
time reference/non-time-reference frames more quickly.
That's worth doing even if we make seeking backwards in compressed files quick,
as it would make "find next {marked, time reference}", and "find previous
{marked, time reference}" in uncompressed files, faster as well.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
