(Illustration by Gaich Muramatsu)
Jan Harkes <jaharkes_at_cs.cmu.edu> writes: > There is no such representation problem as far a I know. RPC2 has always > properly converted to and from network byte order. There are some > packets sent as 'binary blob', such as the reintegration log, the > directory contents (which is exchanged during server resolution) and the > repair fix files. > > Reintegration log is 'endian-corrected' by feeding it through the > MultiRPC2 marshalling code. Directory data has 3 or 4 different > representations, on-disk, in-memory, on-the-wire, and kernel-native, > and has it's limitations (size/# of directory entries). The repair fix > files are in a 'human readable' format and parsed by the server, either > way there are no endianness or 32/64 issues there. > > Just about everything in Coda is based on 32-bit integers even when you > are running on a 64-bit systems, so 64-bits really just gives you more > addressible memory. So have you run across i386 and sparc64 servers, or something like that, and seen the test suite :-) pass? I can't quite tell if you mean 'should work' vs 'has been tested and is known to work'.Received on 2013-07-10 08:01:05