On Wed, Aug 28, 2024 at 10:34 AM Scott Lewis <scottsle...@gmail.com> wrote:
> Question: Is grpc going to switch at some point to 4.x of protobuf > library? Or is it going to stay on 3.X of the protobuf-java library? Is > staying on 3.X a matter of backward compatibility? See https://github.com/grpc/grpc-java/issues/11015 . Protobuf 4.x was fully incompatible with 3.x generated code which gave the ecosystem with no real way to upgrade. Just yesterday protobuf released 4.27.4 which is compatible with 3.x generated code. Also, I know this is a protobuf question, but perhaps one of the grpc folks > will know the answer: For the protobuf library for langauge serialization > interoperatibility (e.g. python and java) is the convention to have > com.google.protobuf versions be same number imply compatibility (e.g. java: > 3.25.3 -> python 3.25.3, or just python 3.X, or ???) > The versions don't need to match at all. Most features you use will work in any language. Some new features may come to one language before another, but it is rare that such cross-language features are added and you can just track the versions it becomes available for the languages you care about. -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CA%2B4M1oNJtZq_eZotf09iNUseDjDV6dzN0cigeDH-ZZ2wVbKGHw%40mail.gmail.com.
smime.p7s
Description: S/MIME Cryptographic Signature
