Hi Jaap (& list),
As the "father" of the "copy as filter" functionality, I would vote for it
to be present all the time in the packet details pane (where I use it most).
Keeping track of all possible filters for the packet list pane seems like an
overkill to me and could be made optional to save memory. Or it should be
implemented in a way where it will dynamically be generated. For 1.2.0 I
would suggest to just revert the implemented memory-consuming patch and
disable the functionality in the packet-list. Then we can decide later to
make it either optional of write code that dynamically generate the filter
string on use (if that is at all possible).
How does that sound?
Sake
----- Original Message -----
From: "Jaap Keuter" <jaap.keuter@xxxxxxxxx>
To: "Developer support list for Wireshark" <wireshark-dev@xxxxxxxxxxxxx>
Sent: Sunday, May 31, 2009 11:02 AM
Subject: [Wireshark-dev] On Copy as Filter
Hi list,
Looking at bug 3489 (which need to be solved in 1.0.9) and the history of
the
"Copy as Filter" feature, with complaints on memory usage, I wonder if we
need
to make this an optional feature. Optional in that it can be selected in
the
user preferences if this features is to be available, hence increase the
memory
footprint. Should this be done in time for 1.2.0?
Thanx,
Jaap
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe