Results (
Thai) 2:
[Copy]Copied!
Computer networks are big endian, which means that when little endian computers
are going to pass integers over the network (network device addresses, for
example), they need to convert them to network byte order. Likewise, when they
receive integer values over the network, they need to convert them back to their
own native representation.
Although you may not be familiar with this little versus big endian debate, it
is important to many current software applications. Any program that writes data
to or reads data from a file must be aware of the byte ordering on the particular
machine. For example, the Windows BMP graphics format was developed on a
little endian machine, so to view BMPs on a big endian machine, the application
used to view them must first reverse the byte order. Software designers of popular
software are well aware of these byte-ordering issues. For example, Adobe Photoshop
uses big endian, GIF is little endian, JPEG is big endian, MacPaint is big
endian, PC Paintbrush is little endian, RTF by Microsoft is little endian, and Sun
raster files are big endian. Some applications support both formats: Microsoft
WAV and AVI files, TIFF files, and XWD (X windows Dump) support both, typically
by encoding an identifier into the file.
Being translated, please wait..
