Hi Bill,
I don't know if the format's developers ever contemplated that use
case - although they designed it to be fairly extensible, and I'm sure
that someone could design a new type of block that stores serialised
application preferences (in compressed XML, JSON, or some other
format?), after requesting an type ID for it.
I haven't thought too much about how you'd actually go about deciding
upon the preferences to store - although adding a universal "Save
Current Preferences" option to the file saving dialogue, and having an
option in the corresponding file opening dialogue to temporarily
import/set those preferences might work.
I'm sure that others will come up with better ideas, though...
Tyson.
On 5 March 2012 18:26, Bill Meier <wmeier@xxxxxxxxxxx> wrote:
> Would it make any sense to be able to store "application specific"
> information in a pcapng file ?
>
> E.g., selected Wireshark prefs so that Wireshark can act on same ?
>
> This would be useful when a capture file reqires specific dissector
> preferences to properly dissect the file.
>
> Would this fit (at all) within the design goals for pcapng ?
> Is there be a way to do this reasonably cleanly with the existing format ?
>
> How might one indicate the prefs which should to be stored ?
>
> ....
>
> Bill
>
> ___________________________________________________________________________
> 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
--
Fight Internet Censorship!
http://www.eff.org
http://vmlemon.wordpress.com | Twitter/FriendFeed/Skype: vmlemon |
00447934365844
