Almost 6 years later, what do you think about this now? What about using https://github.com/dcodeIO/ProtoBuf.js ? or is it still more convenient to simply stick to JSON/BSON/PSON?
-- Leo On Friday, June 26, 2009 at 2:17:58 AM UTC+2, Kenton Varda wrote: > > One problem with javascript and protobuf is that you need a lot of support > code to parse the messages. Unless you end up sending quite a lot of stuff > back and forth, making the user download a JS protobuf codec library may be > a net loss. It may be better to use JSON or XML because browsers already > have built-in support for those. > > That said, I think various people inside google have been playing with > javascript + protocol buffers for awhile and if we end up with anything > that works well enough, we'll release it. > > On Thu, Jun 25, 2009 at 3:23 PM, rthompson.dtisoft....@gmail.com < > rthompson.dtisoft....@gmail.com> wrote: > >> >> Is there anything in the works that would allow us to output >> JavaScript along with C++, Java, and Python? >> >> > -- 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 http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
