Re^3: Best technique to code/decode binary data for inter-machine communication?

Were you using \n as a record separator in your protocol by any chance? Binmode would prevent conversions in transmission, but the clients would be parsing the input differently, and some would never see a "\n" since they're really looking for "\r\n".

Comment on Re^3: Best technique to code/decode binary data for inter-machine communication?

Replies are listed 'Best First'.
Re^4: Best technique to code/decode binary data for inter-machine communication? (newlines) by tye (Sage) on Aug 16, 2012 at 01:14 UTC
some would never see a "\n" since they're really looking for "\r\n" No, lack or presence of a "\r" is not going to mess up line-oriented I/O on any version of Perl¹. Perl on Windows has no problem reading files that lack "\r" characters. Perl on Unix has no problem reading files that contain "\r" characters (it just includes the "\r" in the returned string). But a common mistake with using sockets with Perl is using `<$sock>`, which will hang forever until a newline or end-of-file arrives. (Using `print` on a socket shouldn't to be a problem as sockets shouldn't default to buffered mode.) ¹ Now that ancient Mac Perl's mistake of psuedo ASCII is history. But avoiding binmode wouldn't help in that case anyway. - tye	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^4: Best technique to code/decode binary data for inter-machine communication? (newlines)
by tye (Sage) on Aug 16, 2012 at 01:14 UTC

some would never see a "\n" since they're really looking for "\r\n"

No, lack or presence of a "\r" is not going to mess up line-oriented I/O on any version of Perl¹. Perl on Windows has no problem reading files that lack "\r" characters. Perl on Unix has no problem reading files that contain "\r" characters (it just includes the "\r" in the returned string).

But a common mistake with using sockets with Perl is using <$sock>, which will hang forever until a newline or end-of-file arrives. (Using print on a socket shouldn't to be a problem as sockets shouldn't default to buffered mode.)

¹ Now that ancient Mac Perl's mistake of psuedo ASCII is history. But avoiding binmode wouldn't help in that case anyway.

- tye

[reply]
[d/l]
[select]