Wireshark-dev: Re: [Wireshark-dev] Standard defined field names in Wireshark dissectors
Hi,
We have already make some big change for Wireless (remove mgmt on display filter) and no really a big issue...
About standard for display filter and display filler name, it is complicated... for USB specification, the standard descriptors is not really "name" (bXXXId...)
Cheers
I agree that scripts should not rely on such an output. However sometimes there isn't another option or people just do it anyway. We must consider that as well.
Talking about Tomasz proposal, I agree that we should follow the standards as closely as possible. But if that breaks backward compatibility, I'd suggest to keep it for wirershark 4.0.
Major version changes break backward compatibility, and that looks to be the case.
On Jan 5, 2020, at 8:06 AM, Tomasz Moń <desowin@xxxxxxxxx> wrote:
> In case of the USB Audio descriptor dissection, I would like to change
> the header_field_info name, leaving abbrev as is. Would that still
> cause problems?
It would cause problems for programs that parse TShark -T text (default text) output (or "export the packet dissections as plain text" Wireshark output), but programs should avoid doing that if possible - they should use other -T formats, in which the abbrev is used.
It shouldn't cause problem for any other software; filters, for example, use the abbrev. ("abbrev" should be thought of as the field name, and "name" should be thought of as the field *description*.)
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
--
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
