I'm using protoc as the raw .proto parser for protobuf-net (I then
process the compiled binary for code-generation); at the moment, it is
very sensitive about line endings - if it isn't LF, it won't work.
This creates a bit of a nag for Windows users, as you have to go out
of your way to get the
I'm trying to get the following to work but nothing is being written to
the output stream.
any ideas?
private void testEncode() throws Exception {
OutputStream out = new ByteArrayOutputStream();
CodedOutputStream cos = CodedOutputStream.newInstance(out);
Person.perso
In order to *use* the Java implementation, you need to build that same C++
code -- the protocol compiler. The Java protobuf runtime is mostly useless
without it. However, you can get a prebuilt copy of protoc.exe for windows
here:
http://code.google.com/p/protobuf/downloads/detail?name=protoc-2.1
In order to get the Java implementation I have to compile some C++ code,
but have limited resources on my machine at this time to install a compiler.
Where can I get the Java jar to drop into my project for Win32?
thanks
J.V.
--~--~-~--~~~---~--~~
You received t
That worked! Thanks!
On Jun 30, 5:06 pm, Kenton Varda wrote:
> On Tue, Jun 30, 2009 at 4:28 PM, rthompson.dtisoft@gmail.com <
>
> rthompson.dtisoft@gmail.com> wrote:
>
> > I'm confused. Shouldn't I just create a class called
> > DynamicServiceStub and have it inherit from "class LIBPROT
The Java ME version: http://code.google.com/p/protobuf-javame/
Should work fine with earlier versions of Java, I have however not
tested it.
I had an idea to optimize it for Java 1.4 as well, to offer things
like ArrayList and so on but didn't really know if there was any need
for it.
Let me know
Well, to be fair, Microsoft explicitly says that STL is not allowed to be
used in library interfaces for this exact reason. However, protocol buffers
was designed on a platform that had no such restriction, and we can't very
well rewrite it now just because one platform -- that we don't even use
i
We have our own system. While we would love to open source it in principle,
it is currently tightly coupled to our internal datacenter and machine
configurations, so we can't really release the code as-is. I personally
hope that we manage to get it out eventually but I have no idea if or when
it
Google uses its own internal RPC implementation, and I don't think we can
endorse a particular third-party one as better than the others. I'd tell
you which one I personally found most beneficial, but I have no experience
with any of them.
Cheers,
Alek
On Wed, Jul 1, 2009 at 10:18 AM, J.V. wrot
thanks, which product(s) does Google use internally or find most beneficial?
Kenton Varda wrote:
> You could look at one of the open source RPC implementations listed here:
>
> http://code.google.com/p/protobuf/wiki/ThirdPartyAddOns#RPC_Implementations
>
--~--~-~--~~~
Ok,
using the debug version library with the debug version of the program
fixed the crash.
It is very disappointing to see that in VS20xx such miserable errors
can occur, without any proper error message ("incompatible libraries"
when linking, instead of random crash when executing).
Thanks for t
Thanks Cristopher and Kenton!
I will provide a Mutex to the higher levels as you recommend.
Jes.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to protob
12 matches
Mail list logo
