| 1. | All processors must be designated as either big endian or little endian
任何处理器都必须设计成要么是大端字节序，或者要么小端字节序。 |
| 2. | Little endian architectures require byte - swapping - a slight performance disadvantage for networked applications
低位优先架构要求字节交换对网络应用程序来说，这是一个轻微的性能弱点。 |
| 3. | Little endian means that the least significant byte of any multibyte data field is stored at the lowest memory address , which is also the address of the larger field
小端字节意味着任意多字节数据字段的低位字节存储于低的内存地址中，低内存地址也是大字段的地址。 |
| 4. | For that reason , it may be unwise to select a little endian processor for use in a device , such as a router or gateway , with an abundance of network functionality
正由于该原因，在需要大量网络功能的设备中（比如路由器或者网关） ，使用一个小端字节序的处理器是不明智的。 |
| 5. | Big endian architectures , such as the powerpc , have an advantage over little endian architectures such as the intel pentium series in that network byte order is big endian
高位优先架构（比如powerpc ）比低位优先架构（比如intel pentium系列，其网络字节顺序是高位优先）有优势。 |
| 6. | If the stack will run on a little endian processor , it will have to reorder - at run time - the bytes of every multibyte data field within the various layers ' headers
如果该栈运行于一个小端字节序的处理器上，它不得不在运行时，在不同层的头部，重排每一个多节字数据字段的字节顺序。 |
| 7. | But what happens if a client running on a big endian ibm powerpc attempts to send a 32 - bit integer to a little endian intel x86 ? byte ordering will cause the value to be interpreted incorrectly
但是，如果一个运行在高位优先的ibm powerpc上的客户端发送一个32位的整数到一个低位优先的intel x86 ，那将会发生什么呢？ |
| 8. | My work include : ( 1 ) analyze the architecture of dicom application entity and working mechanism and implement the model of dicom network communication based on tcp / ip . complete the communication between 3 kinds transfer syntax : implicit vr little endian , explicit vr little endian , explicit vr big endian
主要的工作包括： （ 1 ）分析dicom应用实体结构以及运行机制，实现了基于tcp / ip协议的dicom网络通讯模型，完成了具有隐式表示低字节优先字节顺序、显示表示低字节优先字节顺序以及显示表示高字节优先字节顺序三种传输语法的服务对象对的传输。 |
