From: Anh Vo <anhvofrcaus@gmail.com>
Subject: Endian problems - what best way to solve it with least effort
Date: Tue, 13 Mar 2012 11:00:51 -0700 (PDT)
Date: 2012-03-13T11:00:51-07:00 [thread overview]
Message-ID: <10483391.72.1331661651734.JavaMail.geo-discussion-forums@vbdj6> (raw)
I have an application previously running on Big Endian machine communicating with a client simulator through socket. This client is coded in Java running on a separate machine. The data exchanged between them have different structures down to bits and bytes.
Currently, this application is being ported to GNAT running on RH 5.4 (Little Endian PC machine). As the result, both application and client do not communicate correctly any longer due to endian mismatched. The reason is that Java VM uses Big Endian format even though the client runs on a PC.
So far, I have come up with a couple ways. However, each of them involves lots of efforts.
What is the best way to solve it with least effort? Thank you in advance for your suggestion.
Anh Vo
next reply other threads:[~2012-03-13 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 18:00 Anh Vo [this message]
2012-03-13 18:23 ` Endian problems - what best way to solve it with least effort Dmitry A. Kazakov
2012-03-13 18:29 ` Marc C
2012-03-13 18:35 ` Simon Wright
2012-03-14 15:54 ` Anh Vo
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox