We do have a implementation working for node:
https://github.com/google/protobuf/tree/master/js
However, this implementation is assumed to work with closure compiler
<https://developers.google.com/closure/compiler/>.
Without the closure compiler, our implementation is expected to be 6~7X
slower than protobufjs. (Especially for string)

On Fri, Aug 10, 2018 at 1:13 PM Shailesh Kulkarni <05.shail...@gmail.com>
wrote:

> Hi,
>
> I have following requirement.
>
> 1. Server is in the CPP Created from Google Protobuf def.
> 2. Client Application is in Node JS.
> 3. Server and client applications communicate over websocket.
>
> For Client application we are using
> https://www.npmjs.com/package/protobufjs
>
> For some simple messages, the encoded messages in Node JS ProtobufJS are
> same as that one generated from Cpp server (Protobuf).
>
> However I can see that for the nested messages there is a problem.
>
> Do we have node JS support for the Google Protobuf with interoperability
> with other languages such as c++,Java,Python supported as client libraries
> of Google Protobuf?
> If yes then please share the details. If no then please confirm and let me
> know.
>
>
> Regards,
> Shailesh
>
> --
> 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.

Reply via email to