You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the conversion from XL to bytes socket stream, is it correct to say the encoding is in big endian while on Intel the data is in little endian ? if so, is there a reason to do this conversion and not to stay in little endian over the socket ? Or can this be choosen in some way (in the INI file per XLLOOP server) ?
sebastien
The text was updated successfully, but these errors were encountered:
Hi. Yes, you are correct, the xlloop addin is fixed to be big endian. There is currently no way to change this via config. The choice was largely driven by networking standards: http://en.wikipedia.org/wiki/Endianness#Endianness_in_networking. Do you see any issues with the endianness?
On the conversion from XL to bytes socket stream, is it correct to say the encoding is in big endian while on Intel the data is in little endian ? if so, is there a reason to do this conversion and not to stay in little endian over the socket ? Or can this be choosen in some way (in the INI file per XLLOOP server) ?
sebastien
The text was updated successfully, but these errors were encountered: