Kenton,
well, I checked this over and over again and I really think I did make
sure. I also checked the linker settings for all other libs I link
against and they are all set to Debug. Also, this is the same build
environment I used with 2.0.3. where it did work. On the other hand,
it's Microsoft
yeah, I'll have it running twice as fast by the time you are back from
your holiday. ;)
From: Kenton Varda [mailto:ken...@google.com]
Sent: Wednesday, July 15, 2009 7:48 PM
To: Alex Black
Cc: protobuf@googlegroups.com
Sub
If you can find a way to make it faster, please send a patch! :)
On Wed, Jul 15, 2009 at 4:46 PM, Alex Black wrote:
> Thanks, yes performance seems really good, though I wouldn't mind seeing
> the java deserialization faster.
>
> --
> *From:* Kenton Varda [mailto:k
Thanks, yes performance seems really good, though I wouldn't mind seeing
the java deserialization faster.
From: Kenton Varda [mailto:ken...@google.com]
Sent: Tuesday, July 14, 2009 8:06 PM
To: Alex Black
Cc: protobuf@googlegroups.
Hi all,
I will be on vacation and not checking e-mail through July 22nd. I've asked
fellow protobuf dev Jason to help answer questions in the meantime, but if
you see a question that isn't answered and you know the answer, please feel
free to jump in. (That goes for when I'm not on vacation, too.
OK. Make sure that the parameter is optional, with the default matching
gzip's default. Thanks.
On Wed, Jul 15, 2009 at 4:27 PM, Peter Keen wrote:
>
> It doesn't look like it has an existing interface for setting zlib
> options. Reading through the source[1], it looks like it chooses
> Z_BEST_
It doesn't look like it has an existing interface for setting zlib
options. Reading through the source[1], it looks like it chooses
Z_BEST_COMPRESSION (-9 to the gzip command line program) whereas gzip
defaults to -6. I'll work up a patch to pass the compression value
through as another option to
Hmm, probably GzipOutputStream is not setting the same compression
parameters as gzip itself uses by default. I'm happy to accept a patch
fixing this. Does the interface (to GzipOutputStream) currently have a way
to control compression parameters? If not, it probably should.
On Wed, Jul 15, 200
Hi guys,
I'm playing around with protocol buffers for a project at work and I'm
coming across a possibly weird problem. I have the following setup in
my main():
std::cerr << "creating file" << std::endl;
int fd = open("blah.repo", O_WRONLY, O_CREAT);
if ( fd == -1 ) {
std::ce
On Wed, Jul 15, 2009 at 10:56 AM, jasonh wrote:
> Foo f = Foo.newBuilder().mergeFrom(...).setCookie(newCookieVal).build
> ();
There's actually a shortcut for this: the toBuilder() method of the Message
interface returns a Builder that is pre-initialized as a copy of that
message.
--~--~--
DON T LET EXTRA POUNDS PILE UP LIKE THE LEAVES...DON T LET EXTRA POUNDS PILE
UP LIKE THE LEAVES...DON T LET EXTRA POUNDS PILE UP LIKE THE LEAVES...
http://diet123.50webs.com/don-t-let-extra-pounds-pile-up-like-the-leaves.html
http://diet123.50webs.com/don-t-let-extra-pounds-pile-up-like-the-leav
Did you make sure to compile your debug build against a debug build of
libprotobuf? MSVC fails miserably when trying to mix and match debug vs.
release, apparently because the STL classes have different representations
between the two.
On Wed, Jul 15, 2009 at 7:38 AM, Mr Moose wrote:
>
> Hi the
On Jul 15, 5:33 am, Kaj Bjurman wrote:
> Hi,
>
> I have just read the tutorials and the some threads in these forums,
> but there's one thing that I can't find an answer for. I'm currently
> using a router that is responsible to route different messages to
> different servers. The protocol that
Hi there,
I am experiencing crashes in a protocol buffers file using debug build
on windows (VC2005). On Linux, debug or not and on Windows release
everything is fine but when I try to run the code on debug it raises
an assertion to crash right afterwards. I'm using 2.1
here's what the stacktrac
Hi,
I have just read the tutorials and the some threads in these forums,
but there's one thing that I can't find an answer for. I'm currently
using a router that is responsible to route different messages to
different servers. The protocol that we are currently using is a very
simple. Basically h
15 matches
Mail list logo