Service transparency was provided by explicit interface and lookup, which provided decoupling between services and the interfaces between them.
由显式接口和查询提供的服务透明性，可以在服务和服务间的接口之间进行分离。
Nor does it need to know what language or programming interface is supported by the source database, thanks to invocation transparency.
得益于调用透明性，它也不需要知道源数据库所支持的语言或编程接口。
This ability affects the user interface, business logic, and database; in addition, it is necessary to address issues regarding concurrency, data integrity, user transparency, and replication.
这种能力包括使用用户界面、业务逻辑和数据库的能力；此外，必须解决与并发、数据集成、用户透明度和复制相关的问题。
The use of pure abstract C++ explicit interface classes worked against true service invocation transparency, because service clients on non-C++ systems required alternative interface definitions.
使用纯粹的抽象 C++显式接口类与真正的服务调用透明性是矛盾的，因为非 C++系统中的服务客户机需要备用的接口定义。
What language or programming interface is supported by the source databases, for example, whether XQuery or SQL is used, or what dialect of SQL the source supports (invocation transparency)?
源数据库支持什么样的语言和编程接口，例如，是否使用了XQuery或SQL，或者数据源支持何种SQL方言(调用透明性)？
What language or programming interface is supported by the source databases, for example, whether XQuery or SQL is used, or what dialect of SQL the source supports (invocation transparency)?
源数据库支持什么样的语言和编程接口，例如，是否使用了XQuery或SQL，或者数据源支持何种SQL方言(调用透明性)？
应用推荐