thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodolfo Ochoa <rodolfo.oc...@gmail.com>
Subject Re: Error with binary data with node.js
Date Fri, 19 Sep 2014 03:01:24 GMT
on node:
thrift@0.9.1

on java:
libthrift-0.9.1.jar



On Thu, Sep 18, 2014 at 9:09 PM, Randy Abernethy <randy.abernethy@gmail.com>
wrote:

> What version of thrift are you using?
> On Sep 18, 2014 7:46 PM, "Rodolfo Ochoa" <rodolfo.ochoa@gmail.com> wrote:
>
> > I have a Java server sending info to C/Python/node.js clients,
> > I don't have issues with C or Python, only with node.js
> > on Java side, I'm sending a byte array, and if I print the values of this
> > byte array I got:
> > byte codes:  -84 -19 0 5 119 44 0 5 -50 108 0 44 75 73 78 -120 -103 -59
> > -124 3 -92 -121 -98 -104 0 0 0 0 0 0 37 -128 1 3 0 0 0 1 0 0 0 1 0 0 0 0
> 0
> > -78 68 -89
> >
> > but on node.js side I receive:
> > byte codes:  65533 65533 0 5 119 44 0 5 65533 108 0 44 75 73 78 65533
> 65533
> > 324 3 65533 65533 65533 65533 0 0 0 0 0 0 37 65533 1 3 0 0 0 1 0 0 0 1 0
> 0
> > 0 0 0 65533 68 65533
> >
> > this means that some characters were replaced, why? how?
> > how can avoid this behavior?
> >
> >
> >
> > --
> > *Rod.O*
> >
>



-- 
*Rod.O*

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