I would use big endian as it's the Java standard. This would then make
it easier to read/write the files from Input/outputStream (see
DataInputStream) as ByteBuffer would only allow you to do the endian
conversion for file access. You may want to use an Input/outputStream
stream to read/write data in a web service.
Paul
*Paul Austin*
/President/CEO/
Revolution Systems Inc.
+1 (604) 288-4304 x201
www.revolsys.com <http://www.revolsys.com>
Christopher wrote:
Should binary files created with OpenJUMP be big
endian or little endian?
Big endian = java standard, PowerPC, RISC.
Little endian = x86.
I don't have a preference as either would be equally
easy (praise ByteBuffer), but we should have
some sort of standard as it reduces strange bugs...
--Christopher
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel