On Wed, Aug 12, 2009 at 3:27 PM, Noel Fegan wrote:
> You don't happen to have a WSDL to proto file converter by any
> chance? ;-)
No, but I bet you could write an XSLT to do it pretty easily.
>
>
> On Aug 12, 10:56 pm, Kenton Varda wrote:
> > Well there's good news and bad news. The bad new
Ah, I was just talking about the size of the .jar files here, which I had
thought was what you were worried about. The runtime memory use could be
much larger; I'm not sure. In the non-lite runtime, descriptors are
constructed at startup which take space. The lite library does not allocate
any p
We have a UI app (client) that talks to a locally running process
(localhost) which I am calling the server. So, we're using SOAP for
IPC so it's not "remote", but it is an invocation of an out-of-process
functionality. As such both processes are running on the client
machine. We have a number of
Well there's good news and bad news. The bad news is that using protocol
buffers has been known to lead to large code footprints. The good news is
that it should be fairly easy to estimate how much it will bloat *your*
binary, without having to actually implement the whole system.
Protocol buffer
Hi,
This might be a "how long is a piece of string"-type question, but I
was wondering if there's any way for me to know how much protocol
buffers might add to my app's memory footprint, when I have a large
number of messages. I see there's a LITE option which sounds like the
mode I would need to
