thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Herou" <marcus.he...@tailsweep.com>
Subject Re: [thrift] Serialization
Date Sat, 07 Jun 2008 16:58:38 GMT
I'm not 100% sure why I switched, was thinking that the clients could send
Base64 encoded strings back and forths but to be honest that's a little
lame.

It's 5 mins work to switch back and I will do so...

/M

On Sat, Jun 7, 2008 at 6:52 PM, Johan Stuyts <j.stuyts@zybber.nl> wrote:

> The only real constraint currently will be that the client need to
>> encode/decode objects to a string representation. I initially made the
>> cache
>> store byte[] but switched to strings.
>>
>
> Why did you make the switch? Thrift has a binary type which does what you
> need and is supported by all language bindings. Using 'binary' should remove
> the need to encode the data as strings on the client side.
>
> --
> Kind regards,
>
> Johan Stuyts
>



-- 
Marcus Herou CTO and co-founder Tailsweep AB
+46702561312
marcus.herou@tailsweep.com
http://www.tailsweep.com/
http://blogg.tailsweep.com/

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message