240.chr different on Linux than Windows?

Rails
1

I’m sending a string through a socket connection from a rails app to
another application. The string is delimited with 240.chr. On windows it
runs fine, on Linux, it seems to put in a different looking character in
for 240.chr. Is this some sort of encoding issue? Is there something
simple
I am overlooking? Thanks, RVic.

delim = 240.chr
if userSelected.blank?
  userSelected = userSending
end

s=row.to_s+delim+userSending+delim+userSelected+delim+message+delim+notes

2

On Nov 7, 2013, at 7:54 PM, RVic [email protected] wrote:

I'm sending a string through a socket connection from a rails app to another

application. The string is delimited with 240.chr. On windows it runs fine, on
Linux, it seems to put in a different looking character in for 240.chr. Is this
some sort of encoding issue? Is there something simple I am overlooking? Thanks,
RVic.

delim = 240.chr
if userSelected.blank?
  userSelected = userSending
end
s=row.to_s+delim+userSending+delim+userSelected+delim+message+delim+notes

If youre using 240.chr as a delimiter, what difference does it make what
the Glyph looks like? The other side should just split on 240.chr.

3

I would think so, but the other side is a java socket listener app, and
it
isn’t splitting on it in Linux, but is on Windows.

4

On Nov 7, 2013, at 8:20 PM, R Vince [email protected] wrote:

if userSelected.blank?
  userSelected = userSending
end
s=row.to_s+delim+userSending+delim+userSelected+delim+message+delim+notes

If youre using 240.chr as a delimiter, what difference does it make what the
Glyph looks like? The other side should just split on 240.chr.

You need to be looking at the binary data stream to see what is being
sent/received. Dont look at the glyphs at all.

5

On Thu, Nov 7, 2013 at 9:32 PM, Tamara T.
[email protected]wrote:

You need to be looking at the binary data stream to see what is being
sent/received. Dont look at the glyphs at all.

Yes, you;re right – I need to open up the receiving end and see what
it’s
drinking in. Thanks!