javascript (including browsers and node.js) can handle binary data just fine, and my understanding is that this functionality is exposed by the javascript implementation. I can't opine on that hugely, because my use of protobuf is primarily backend - server-to-server, or server<--->storage.
Advantages: - performance - size - schema definition On 23 Jun 2017 7:53 a.m., <exoticaru...@gmail.com> wrote: Thank you for your reply. i'm able to get a better picture now. I also read that the byte stream which is produced can't be read by the modern browsers which is why we have to convert it into json using gwt(google web toolkit) or something like that. So automatically json is used here. Then what makes protobufs advantageous than json. Is there any advantage other than protobufs are structured? what makes google use protobufs almost everywhere in their data transmission? On Wednesday, June 21, 2017 at 9:17:15 AM UTC+5:30, exotic...@gmail.com wrote: > > Being a student, I need to know where we really use protobufs in. A > clearer picture is required. Also tell me how it can be applied in the > client - server communication cases. > Thank you. > -- 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 protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout. -- 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 protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.