[protobuf] Silly beginner question: Do the different RPC implementations inter-work?
So, say I took a Java implementation from somewhere, and a C++ implementation from somewhere else, and a C# implementation from somewhere else, would they just easily inter-work (say if I specified the same transport channel or something)? If not, is it easy to make them inter-work? Is it a good idea or practical to try to do so? If so, what are the basic steps? If not, does anybody know of a truly cross-platform, scalable RPC protobuf-based library coming up? -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Newbie question - Java Build
I'm having an issue on building the jar version and I can not figure out why. D/L'ed the source and compiled the C++. I'm on Windows 7 so I used the VS C++. Moved the protoc.exe to the Java/src directory. I also moved it to another directory in that is in my PATH. When I run 'mvn test' I get an Ant BuildException can not run program../src/protoc: System cannot find the file specified' I followed the instructions for compiling the C++ and Java. I even D/ L'ed the windows binary and put it in the java/src directory with the same result. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] Re: Silly beginner question: Do the different RPC implementations inter-work?
Navigateur wrote: Did you use the automatically-generated abstract service code, or did you do the recently recommended make your own code-generator plugin to do the implementation? My implementation was started before the code generation plugins were done, so I used the existing abstract service. Were I to start it today, I would use the code generator, since there are a few small things in the automatically generated RPC interface that I would like to change. Evan -- Evan Jones http://evanjones.ca/ -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Silly beginner question: Do the different RPC implementations inter-work?
Did you use the automatically-generated abstract service code, or did you do the recently recommended make your own code-generator plugin to do the implementation? What do you think of these 2 alternatives? On Aug 27, 3:43 pm, Evan Jones ev...@mit.edu wrote: Navigateur wrote: So, say I took a Java implementation from somewhere, and a C++ implementation from somewhere else, and a C# implementation from somewhere else, would they just easily inter-work (say if I specified the same transport channel or something)? Almost certainly not. While the service definitions and the data format are defined by the protobuf library, an RPC implementation needs to pass some additional data between the end points (eg. what method to invoke, potentially other options). The format of this data is not specified, so implementations are incompatible. If not, is it easy to make them inter-work? Is it a good idea or practical to try to do so? If so, what are the basic steps? I suspect it wouldn't be very difficult. Mostly it would be an issue of having a bunch of implementors agree on a wire protocol. However, as a third party, I suspect it would be hard, since you won't understand the protocol. I think part of the issue is that most people roll their own interchange protocol on top of protocol buffers, since it is pretty easy to do. However, if you want a ready to use RPC system, protocol buffers aren't your best choice. That said: If you are desperate and willing to put in some effort, I have a C++ and Java implementation of the protocol buffers RPC interfaces that I've been using. It isn't the best thing in the world, and you'll need to put in some effort to get it to work in some other project, but it is available under a BSD license. Hope this helps, Evan -- Evan Joneshttp://evanjones.ca/ -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
