Hy,
I'm using protocoll buffers to share data between python and java with
xmlrpc.
I've implemented a method in python that returns a string that is the
result of invoking, in Python
object.serializeToString()
My rpc client while reading the response returns:
An invalid XML character (Unicode
It is mentioned in this post:
http://groups.google.com/group/protobuf/browse_thread/thread/a0098a395e0ec63c
That to cross compile you just need build the library.
What are the targets for the building just the runtime libraries?
-- Wink
--~--~-~--~~~---~--~~
You
I think this should do it:
cd src
make libprotobuf.la
On Sat, Jan 24, 2009 at 12:11 PM, Wink wrote:
>
> It is mentioned in this post:
>
> http://groups.google.com/group/protobuf/browse_thread/thread/a0098a395e0ec63c
> That to cross compile you just need build the library.
> What are the tar
The protocol buffer encoding is a binary format. SerializeToString()
actually returns a string containing raw bytes, not text. XML doesn't allow
you to embed raw bytes into it, so you will have to base-64 encode them.
It's probably better to avoid using XML altogether if you can. Embedding a
pr
Hi,
I am new to Protocol Buffers. I knew Google released them sometime ago, but
I have started looking into it just this week. Without further ado, the real
reason for seeking an alternative to our current WSDl, XML, SOAP is that its
a mess, high maintainence, not fast enough.
Background:
Our pro
