ICE Manual(Documentation for Ice 3.5)---The Ice Protocol(Data Encoding)
来源:互联网 发布:满汉大餐方便面 知乎 编辑:程序博客网 时间:2024/05/19 20:42
The key goals of the Ice data encoding are simplicity and efficiency. In keeping with these principles, the encoding does not align primitive types on word boundaries and therefore eliminates the wasted space and additional complexity that alignment requires. The Ice data encoding simply produces a stream of contiguous bytes; data contains no padding bytes and need not be aligned on word boundaries.
Data is always encoded using little-endian byte order for numeric types. (Most machines use a little-endian byte order, so the Ice data encoding is "right" more often than not.) Ice does not use a "receiver makes it right" scheme because of the additional complexity this would introduce. Consider, for example, a chain of receivers that merely forward data along the chain until that data arrives at an ultimate receiver. (Such topologies are common for event distribution services.) The Ice protocol permits all the intermediates to forward the data without requiring it to be unmarshaled: the intermediates can forward requests by simply copying blocks of binary data. With a "receiver makes it right" scheme, the intermediates would have to unmarshal and remarshal the data whenever the byte order of the next receiver in the chain differs from the byte order of the sender, which is inefficient.
Ice requires clients and servers that run on big-endian machines to incur the extra cost of byte swapping data into little-endian layout, but that cost is insignificant compared to the overall cost of sending or receiving a request.
- ICE Manual(Documentation for Ice 3.5)---The Ice Protocol(Data Encoding)
- ICE Manual(Documentation for Ice 3.5)---The Ice Protocol(Basic Data Encoding)
- ICE Manual(Documentation for Ice 3.5)---The Ice Protocol(Protocol and Encoding Versions)
- ICE Manual(Documentation for Ice 3.5)---The Ice Protocol(Overview)
- ICE Manual(Documentation for Ice 3.5)---The Ice Protocol(Protocol Messages)
- ICE Manual(Documentation for Ice 3.5)---The Ice Protocol(Protocol Compression)
- ICE Manual(Documentation for Ice 3.5)---The Ice Protocol(与IIOP对比)
- ICE Manual(Documentation for Ice 3.5)---The Ice Protocol(与IIOP对比)
- ICE Manual(Documentation for Ice 3.5)---The Ice Run Time in Detail(Time Out)
- ICE Manual(Documentation for Ice 3.5)---The Ice Run Time in Detail(Logger Facility)
- ICE Manual(Documentation for Ice 3.5)---The Ice Run Time in Detail(Location Transparency)
- ICE Manual(Documentation for Ice 3.5)---The Ice Run Time in Detail(Automatic Retries)
- ICE Manual(Documentation for Ice 3.5)---Slice
- ICE Manual(Documentation for Ice 3.5)---IceGrid
- ICE Manual(Documentation for Ice 3.5)---The Ice Run Time in Detail(ICE Stats)
- ICE Manual(Documentation for Ice 3.5)---Ice Architecture--Terminology
- ICE Manual(Documentation for Ice 3.5)---Ice Architecture--异常信息
- ICE Manual(Documentation for Ice 3.5)---Ice Architecture--Architectural Benefits of Ice
- 学习openTLD 资源
- android笔记01 AppWidgetProvider
- 编程巨星的唯一秘诀
- 《洛克菲勒留给儿子的38封信》
- Image Sharpen
- ICE Manual(Documentation for Ice 3.5)---The Ice Protocol(Data Encoding)
- mysql重要参数配置
- session
- 用Flash Builder 4 beta建立连接BlazeDS远程端的Flex应用程序
- IplImage轉CBitmap
- 双链表的实现
- Make: Nothing to be done for 'all'. Make: Nothing to be done for 'default'.
- Junit4的使用及实例
- nagios core安装