C++11 Mapping支持的Ice 3.7.0手册：开发者指南

需积分: 9 106 浏览量更新于2024-07-19 收藏 10.47MB PDF 举报

ZeroC Ice Manual 3.7.0 是一份全面的指南，专门面向那些希望利用 Ice（Internet Communication Engine）进行分布式应用程序开发的开发者。此版本特别强调了对C++11 Mapping的支持，这对于C++开发者来说是一个重要的升级，因为它允许更灵活地映射C++类型到Ice的通信模型。 1. Ice概述： Ice架构基于模块化的设计，术语包括"slice"（一种规格语言），用于定义服务接口和操作。它采用了一种独特的语言映射机制，允许开发者将C++、C#、Java、JavaScript、Objective-C、PHP、Python和Ruby等多种编程语言的特性无缝融入到Ice框架中。 1.1.1 Ice语言与架构： - 术语：文档解释了诸如"adapter"（适配器）、"proxy"（代理）和"stub"（stub）等核心概念，这些在Ice的通信过程中扮演着关键角色。 - Slice：作为主要的规格语言，它定义了服务的接口和行为，支持用户自定义类型，使得服务的描述更加灵活。 - 语言映射：章节详述了如何将C++11的新特性和类型映射到Ice，如模板、泛型和智能指针等，提高了代码的可读性和效率。 1.1.1.4 客户端和服务器结构： Ice设计注重分离关注点，客户端和服务端通过序列化和反序列化过程进行通信，而Ice协议则提供了透明的数据传输和错误处理机制。 1.1.2 Ice服务概述： Ice支持多种服务模式，包括主动-被动、主动-主动和被动-被动，以及异步通信，这使得开发者可以根据应用场景选择最适合的解决方案。 1.2 示例应用：教程部分展示了如何使用不同语言编写Hello World应用，从C++11版本开始，逐个介绍了C++98、C#、Java、Java Compat、JavaScript、Objective-C、PHP、Python和Ruby的示例，以便读者实际体验并理解各种语言的用法。 1.3 Slice语言深度解析：该部分深入探讨了slice的编译流程、源文件组织、语法细节（如关键字、标识符规则）以及模块化编程，确保开发者能够创建高效且易于维护的Ice服务。 ZeroC Ice Manual 3.7.0 不仅是一份入门指南，还提供了一套完整的工具和技术，帮助C++开发者充分利用C++11 Mapping的优势，同时支持其他语言的开发者在Ice平台上实现高效的分布式应用程序开发。无论是初学者还是经验丰富的开发者，都能从中找到所需的信息和指导。

Ice 3.7.0 Documentation

Ice Manual

Distributed Programming with Ice

The Internet Communications Engine (Ice) is an object-oriented RPC framework that helps you build distributed applications with minimal

effort. Ice allows you to focus your efforts on your application logic, and it takes care of all interactions with low-level network programming

interfaces. With Ice, there is no need to worry about details such as opening network connections, serializing and deserializing data for

network transmission, or retrying failed connection attempts.

The main design goals of Ice are:

Provide an object-oriented RPC framework suitable for use in heterogeneous environments.

Provide a full set of features that support development of realistic distributed applications for a wide variety of domains.

Avoid unnecessary complexity, making the platform easy to learn and to use.

Provide an implementation that is efficient in network bandwidth, memory use, and CPU overhead.

Provide an implementation that has built-in security, making it suitable for use over insecure public networks.

In simpler terms, the Ice design goals could be stated as "Let's build a powerful middleware platform that makes the developer's life easier."

Getting Help with Ice

If you have a question and you cannot find an answer in this manual, you can visit our to see if another developer hasdeveloper forums

encountered the same issue. If you still need help, feel free to post your question on the forum, which ZeroC's developers monitor regularly.

Note, however, that we can provide only limited free support in our forums. For guaranteed response and problem resolution times, we

highly recommend purchasing .commercial support

Feedback about the Manual

We would very much like to hear from you in case you find any bugs (however minor) in this manual. We also would like to hear your opinion

on the contents, and any suggestions as to how it might be improved. You can contact us via e-mail at .icebook@zeroc.com

Legal Notices

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those

designations appear in this book and ZeroC was aware of the trademark claim, the designations have been printed in initial caps or all caps.

The authors and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and

assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising

out of the use of the information or programs contained herein.

License

This manual is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.

The acronym "Ice" is pronounced as a single syllable, like the word for frozen water.

Ice 3.7.0 Documentation

Terminology

Every computing technology creates its own vocabulary as it evolves. Ice is no exception. However, the amount of new jargon used by Ice is

minimal. Rather than inventing new terms, we have used existing terminology as much as possible. If you have used another middleware

technology in the past, you will be familiar with much of what follows. (However, we suggest you at least skim the material because a few

terms used by Ice differ from the corresponding terms used by other middleware.)do

On this page:

Clients and Servers

Ice Objects

Proxies

Stringified Proxies

Direct Proxies

Indirect Proxies

Direct Versus Indirect Binding

Fixed Proxies

Routed Proxies

Replication

Replica Groups

Servants

At-Most-Once Semantics

Synchronous Method Invocation

Asynchronous Method Invocation

Asynchronous Method Dispatch

Oneway Method Invocation

Batched Oneway Method Invocation

Datagram Invocations

Batched Datagram Invocations

Run-Time Exceptions

User Exceptions

Properties

Clients and Servers

The terms and are not firm designations for particular parts of an application; rather, they denote roles that are taken by parts ofclient server

an application for the duration of a request:

Clients are active entities. They issue requests for service to servers.

Servers are passive entities. They provide services in response to client requests.

Frequently, servers are not "pure" servers, in the sense that they never issue requests and only respond to requests. Instead, servers often

act as a server on behalf of some client but, in turn, act as a client to another server in order to satisfy their client's request.

Similarly, clients often are not "pure" clients, in the sense that they only request service from an object. Instead, clients are frequently

client-server hybrids. For example, a client might start a long-running operation on a server; as part of starting the operation, the client can

provide a to the server that is used by the server to notify the client when the operation is complete. In that case, the clientcallback object

acts as a client when it starts the operation, and as a server when it is notified that the operation is complete.

Such role reversal is common in many systems, so, frequently, client-server systems could be more accurately described as sypeer-to-peer

stems.

Ice Objects

An is a conceptual entity, or abstraction. An Ice object can be characterized by the following points:Ice object

An Ice object is an entity in the local or a remote address space that can respond to client requests.

A single Ice object can be instantiated in a single server or, redundantly, in multiple servers. If an object has multiple simultaneous

instantiations, it is still a single Ice object.

Each Ice object has one or more . An interface is a collection of named that are supported by an object. Clientsinterfaces operations

issue requests by invoking operations.

An operation has zero or more as well as a . Parameters and return values have a specific . Parametersparameters return value type

are named and have a direction: in-parameters are initialized by the client and passed to the server; out-parameters are initialized

by the server and passed to the client. (The return value is simply a special out-parameter.)

An Ice object has a distinguished interface, known as its . In addition, an Ice object can provide zero or more alternatemain interface

interfaces, known as . Clients can select among the facets of an object to choose the interface they want to work with.facets

剩余3235页未读，继续阅读

无聊的闹钟

粉丝: 2
资源: 5

C++11 Mapping支持的Ice 3.7.0手册：开发者指南

Ice 3.7.0：跨平台下载与安装指南（含源码）

Ice3.7.0技术手册：架构与多语言应用开发

BehaviorTree.CPP-3.7.0版本回顾与3.7.0版本的使用分享

Ice Manual(3.7.0/3.7.1)

ice_3.7.0_linux版

ice_3.7.0_windows版

Ice-3.7.0 下载地址、安装及源码

ice-demos-3.7.0

Python库 | zeroc_ice-3.7.0-cp36-cp36m-win_amd64.whl

ice.jar(3.7.0版本)

最新资源