I don't think there is any way to force enums to use the fixed32 format; they will always be serialized as varints.
One thing to note is that varints are not an optional compression step, they're an important part of the wire format <https://developers.google.com/protocol-buffers/docs/encoding>. I suspect it would be much easier to get Wireshark to decode the varints for you than it would be to try to avoid all varints. On Wed, Jul 31, 2019 at 1:03 AM Alexandre SIMON <[email protected]> wrote: > Thanks for your reply, I already found why it doesn't work: uint32 in > proto file is converted in varint in line... So I changed uint32 to fixed32 > but a second question happen: > How to force enum to be a fixed32 and not a uint32 (converted in varint)? > > Le mardi 30 juillet 2019 23:46:08 UTC+2, Adam Cozzette a écrit : >> >> I'm not sure what kind of compression gRPC does, but there is a GitHub >> issue here with some instructions on decoding gRPC packets with Wireshark: >> https://github.com/grpc/grpc/issues/13586 >> >> On Mon, Jul 29, 2019 at 11:57 PM Almon <[email protected]> wrote: >> >>> Hi everyone, >>> >>> In my project, I use Grpc to exchange messages between server and client >>> by ethernet and I want to dissect in Wireshark all the messages (and >>> embedded messages) who are exchanged. >>> I have some troubles to dissect embedded message because I see it >>> compressed. For example, my embedded message is 24 bytes length but I see >>> it at 8 bytes length. Althrough, in wireshark, I see the main message not >>> compressed... >>> >>> Someone know if it's a parameter to set or if it's a grpc internal >>> process? >>> Else, do we could find the compression algorithm to uncompress embedded >>> message? >>> >>> Thank you for your help. >>> >>> Alexandre. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Protocol Buffers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/protobuf/bf597ee7-6a69-4abf-9e95-d4917bbbab7d%40googlegroups.com >>> <https://groups.google.com/d/msgid/protobuf/bf597ee7-6a69-4abf-9e95-d4917bbbab7d%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/protobuf/8a447438-a7c0-4a7e-b5a0-d1fc7d0869b2%40googlegroups.com > <https://groups.google.com/d/msgid/protobuf/8a447438-a7c0-4a7e-b5a0-d1fc7d0869b2%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/protobuf/CADqAXr7mUnOynK2UgVPTN1bqMfw2KbYkr0Bp_qiSkqjBfzr0uQ%40mail.gmail.com.
