3 ms·
> It's actually the only one I've ever used, because why would you not? Because it’s not part of the protobuf specification, not part of a valid protobuf messa
by catiopatio 3y ago
> It's actually the only one I've ever used, because why would you not?
Because it’s not part of the protobuf specification, not part of a valid protobuf message, and framing is a transport/file format concern and should not be performed by default.
If someone is expecting to receive a protobuf-encoded payload, it must not include a framing header.
> If your implementation doesn't support something in the reference implementation, that seems like your problem, not anyone else's.
Someone else’s failure to follow the spec is not our problem.
- whywhywouldyou 3y agoOP just told you it was in the spec, and then linked you directly to it. You're just repeating your previous post without adding anything new. Here's a more direct link: https://protobuf.dev/reference/csharp/api-docs/class/google/protobuf/message-parser#class_google_1_1_protobuf_1_1_message_parser_1a47e94dd6d35594250a54858f99bc5b28 https://protobuf.dev/reference/csharp/api-docs/class/google/...