2014-11-03 18:40 GMT+01:00 Joost Kraaijeveld <J.Kraaijeveld@askesis.nl>:

On ma, 2014-11-03 at 18:33 +0100, Vincenzo Romano wrote:

...

Can you clear there is no networking issue? I mean, can you normally open such sockets between "inter-racial" machines (with networking tools)? I can telnet, ssh and see webpages from Windows to Linux and vice versa. Don't have a mac at hand to personally verify it, but I get reports from my students that the can browse.

Then I would investigate the issue with tools like wireshark and application logging.

On 11/03/2014 06:30 PM, Joost Kraaijeveld wrote: No known issue. I suspect that the recipient cannot parse the exchanged data correctly. Mmmm. Why should that only affect inter-os connections? It is just 1

On ma, 2014-11-03 at 18:40 +0100, Bjorn Reese wrote: program, 1 source base, compiled multi-platformed...

2014-11-03 18:54 GMT+01:00 Bjorn Reese <breese@mail1.stofanet.dk>:

On 11/03/2014 06:44 PM, Joost Kraaijeveld wrote:

...

Mmmm. Why should that only affect inter-os connections? It is just 1 program, 1 source base, compiled multi-platformed...

It depends on the exchange format that you use. If it is binary, and you have made no special encoding, then it could be an 32 vs 64 bit issue, alignment/padding, or endianess.

... I would skip the endianess issue, at least for the Linux/Windows mismatch. I still recommend to use tools like wireshark to inspect the actual handshake and communication stream.