Here it is:
http://code.google.com/p/protobuf-j2me/
--
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...@googlegr
On Fri, Jul 30, 2010 at 3:47 AM, David wrote:
> Hi all, I was finally able to write protocol buffers code over REST
> and did some comparison with XStream which we are currently uses.
> Everything seems great, only stumble with one thing.
>
> We have very large messages in one particular attribut
(adding the mailing list back)
You may need to run the configure command with --with-zlib=[path] or
--system-zlib.
Yes, you can use GzipOutputStream with CodedOutputStream.
On Thu, Jul 29, 2010 at 1:16 PM, Julian González wrote:
> Well, the thing is that I try to use them but first I got an err
Comment #6 on issue 210 by aantono: Java code should detect incompatible
runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
In java, the same can be done when publishing the protobuf-java.jar.
Right now, if you look into the 'java' folder of the project, the pom.xm
Comment #5 on issue 210 by ken...@google.com: Java code should detect
incompatible runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
Kenton, one of the reasons we've created the "shared" model artifact
that is
pre-compiled is to avoid re-generation of src files
What exactly do you want to know about them? There are various details about
how they adapt zlib to the ZeroCopy*Stream interfaces, but as a client you
shouldn't need to worry about that. You can use them just like any other
ZeroCopyStream.
On Thu, Jul 29, 2010 at 8:58 AM, Julian González wrote:
Hi all, I was finally able to write protocol buffers code over REST
and did some comparison with XStream which we are currently uses.
Everything seems great, only stumble with one thing.
We have very large messages in one particular attributes, say
something like this
message Data {
optional s
Comment #4 on issue 210 by aantono: Java code should detect incompatible
runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
Kenton, one of the reasons we've created the "shared" model artifact that
is pre-compiled is to avoid re-generation of src files and recom
Updates:
Summary: Java code should detect incompatible runtime library version
Status: Accepted
Comment #3 on issue 210 by ken...@google.com: Java code should detect
incompatible runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
Yes, only exact ver
Comment #2 on issue 210 by jacob.tomaw: Broken backwards compatibility of
protobuf-java library between 2.0.x and 2.3.x
http://code.google.com/p/protobuf/issues/detail?id=210
What is the expected compatibility between the library and protoc? Only
exact versions are ever compatible?
--
Yo
Updates:
Status: WontFix
Comment #1 on issue 210 by ken...@google.com: Broken backwards
compatibility of protobuf-java library between 2.0.x and 2.3.x
http://code.google.com/p/protobuf/issues/detail?id=210
protoc and the runtime library are tightly coupled. You cannot use an
older
Status: New
Owner: ken...@google.com
Labels: Type-Defect Priority-Medium
New issue 210 by aantono: Broken backwards compatibility of protobuf-java
library between 2.0.x and 2.3.x
http://code.google.com/p/protobuf/issues/detail?id=210
What steps will reproduce the problem?
1. Generate java sou
How the GzipOutputStream and GzipInputStream works?
--
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...@googlegro
It makes sense - thanks for the explanation!
btw I would recommend that we add this info to the official protobuf
documentation (currently it is available only in the changelog)
- Srivats
On Wed, Jul 28, 2010 at 1:54 AM, Kenton Varda wrote:
> Consider the case where you define a message Foo in
Comment #10 on issue 153 by zkfarmer: 2.3 Python code not importing
http://code.google.com/p/protobuf/issues/detail?id=153
when import the module that generated by protoc in python shell, the error
reproduced.
I think that protoc compiler and the python's version of protobuf don't
match, m
15 matches
Mail list logo
