On 10/16/2012 06:17 PM, Rajesh Khan wrote:
Ill have a look at Google Protocol however I would appreciate other ideas
too.
I would go with Andy's original suggestion myself (i.e. a nested map for
each object, with all its fields as entries in the map). You can even
have a special field name id
+1, I have seen this working already in a qpid project.
- Original Message -
> From: "Andy Goldstein"
> To: users@qpid.apache.org
> Sent: Tuesday, October 16, 2012 6:48:15 PM
> Subject: Re: Sending objects to receivers
>
> You could use something like Googl
Ill have a look at Google Protocol however I would appreciate other ideas
too.
On Tue, Oct 16, 2012 at 10:48 AM, Andy Goldstein
wrote:
> You could use something like Google Protocol Buffers to encode your object
> as a binary string to send it over the wire.
>
> Andy
>
> On Oct 16, 2012, at 12:46
You could use something like Google Protocol Buffers to encode your object as a
binary string to send it over the wire.
Andy
On Oct 16, 2012, at 12:46 PM, Rajesh Khan wrote:
> Thats an idea. However I was curious is there a better way to do this ?
> What if my object has lots of properties
>
>
Thats an idea. However I was curious is there a better way to do this ?
What if my object has lots of properties
On Tue, Oct 16, 2012 at 10:44 AM, Andy Goldstein
wrote:
> Could you just take your class's properties and place them in a map?
>
> Andy
>
> On Oct 16, 2012, at 12:29 PM, Rajesh Khan wr
Could you just take your class's properties and place them in a map?
Andy
On Oct 16, 2012, at 12:29 PM, Rajesh Khan wrote:
> While studying QPIDD I realized that I could send maps and lists to
> receivers like this
>
>qpid::types::Variant::Map content;
>content["id"] = 9
