The typical solution to this problem is to agree on an
"on-the-wire" representation, so that each machine
(big-endian or little-endian) _knows_ that whatever
is coming through the pipe is in a given format. If
the on-the-wire format is different than that of the
device -- whether that device is reading -or- writing
to the pipe -- then it is up to it to parse (or produce)
the proper on-the-wire format.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
"Richard Burmeister" <[EMAIL PROTECTED]> wrote in message
news:53490@palm-dev-forum...
>
> > From: Phillip Streck
> > Could the fact that the mortorial proc uses big endian
> > and the intel proc uses little endian have anything to
> > do with not properly decrypted data? thanks
> >
>
> Anytime you create some numbers on one platform and read them on another,
> you have to take into account the possibility that one machine may be "big
> endian" and the other may be "little endian". For example, if one machine
> stores decimal 2004 as the sequence of bytes 07, then D4, then the other
> might interpret those bytes as decimal 54279. (It would expect 2004 to be
> stored as D4, then 07.)
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
