荔园在线
荔园之美，在春之萌芽，在夏之绽放，在秋之收获，在冬之沉淀
[回到开始]
[上一篇][下一篇]
发信人: Jobs (温少), 信区: Visual
标 题: Windows开放服务体系(特别推荐）
发信站: BBS 荔园晨风站 (Wed Dec 1 14:34:16 1999), 站内信件
这篇文章引自《Windows Architecture 1 Study Guide》，这篇文章是我手工输入，输得很
辛苦，也经过了排版，希望对大家了解Windows下编程有所帮助。我正在把文章翻译为中文
，
希望能够尽快把译文发布给大家。
Windows Open Services Architecture(Windows开放服务结构)
The Windows Open Service Architecture(WOSA) is Microsoft's standard
to provide an open environment for Windows-based applications. WOSA takes
a far broader stance than an API by proposing an architecture for integration
between the Windows operating system and Windows-based applications under the
cloak of heterogeneous enterprise-wide computing environment.
To this end, WOSA offers standards for seamless access in three categories
of information resource services: common application services, communication
services, and vertical market services.
The standards for WOSA’s component services are being defined through the
Open Process program with the cooperation for hardware manufacturers,
corporate developers, and independent software vendors. While the WOSA
development effort enjoys wide backing by hundreds of industry members,
Microsoft has also adopted de jure specifications where gaps exist.
Like the Microsoft Foundation Classes(MFC), the WOSA APIs function as a very
thin layer over the Windows API, wrapping the functionality of Windows without
adding unnecessary overhead.
Common Application Services
The use of a consistent and open architecture is intended to allow Windows
based applications to transparently access key services across multiple
software vendors’ implementations, including services, including services
which span different hardware and operating system environments. Among these
services are ODBC, MAPI, TAPI, and LSAPI.
Open Database Connectivity (ODBC)
Open Database Connectivity will be covered in more detail in chapters 9 and
10. In brief, ODBC offers a common method of data access from a variety of
heterogeneous environments. ODBC is an open standard defined by a number of
industry groups including ANSI, the SQL Access Group, X/Open, and others, The
objective behind ODBC was to develop an open and vendor-neutral standard. As a
portable API, ODBC offers cross-platform support for data access from both the
Windows and Macintosh environments.
Messaging API (MAPI)
The Messaging API, like ODBC, is an open standard developed in cooperation
with a broad base of independent software vendors to offer a common method for
windows-based applications to gain access to a wide variety of electronic
messaging services in enterprises environments.
MAPI standards allow a single application – for example, a workgroup
scheduling application – to gain access to all aspects of a company’s
messaging systems, including e-mail systems, voice mail, and fax.
MAPI has been refined in consultation with XAPIA, the standard-setting body
for X.400 communications.
Windows Telephony (TAPI)
The Windows Telephony API (TAPI) offers easy access for applications to
interact with the telephone network. It facilitates visual call control, and
allows fro the integration for electronic mail, voice mail, and fax, as well
as the support of desktop audio and video conferencing.
The TAPI specification has been developed in cooperation with major companies
in the telecommunications and PC industries, including chip manufacturers,
network operators. PC vendors, software developers, telephone system
companies, and voice-mail providers. In response , every major PBX manufacture
has announced support for TAPI and has agreed to offer access to their
previously closed and proprietary PBX systems.
License Service API(LSAPI)
The License Service API is designed to automate software licensing and to
reduce t\her overhead involved in implementing custom licensing systems. The
LSAPI has been developed in cooperation with industry participants including
the Software Publishers Association and the Microcomputer Managers
Association.
Network Communication Services
The existing multiplicity of network standards has been a major stumbling
block to application development and is one of the areas addressed by the
Windows Open Servers Architecture. Services include SNA API. Sockets API, and
the RPC API.
Windows SNA API
The SNA API offers a standard for corporate-host connectivity by providing
open access to the existing IBM SNA API categories.
Windows Sockets API
The Windows Sockets API is used to integrate both Windows and Unix-based
applications across a network. The Sockets API provides a single Windows –
based application interface supporting communications with Sockets-based
applications through a variety of transport protocols including TCP/IP,
AppleTalk, and IPX/SPX.
Microsoft Remote Procedure Call (RPC)
The Microsoft RPC API supports the Open Software Foundation’s Distributed
Computing Environment (DCE) RPC.
Vertical Market Extensions
WOSA has announced a number of vertical market extensions which provide
specialized services to support or extend tasks required by particular market
segments. These include:
Financial Services. Working in cooperation with the Banking Systems Vendor
Council, WOSA defines a standard API extension for branch banking
applications. This API includes functions for varying services, such as
receipt printers and magnetic PIN-pads.
Real-Time Market Data. The Open Market Data Council for Windows – a group of
market data vendors, trading, and brokerage systems suppliers – initiated the
development of WOSA extensions to permit Windows – based applications to
receive live market data, including stock quotes and news. The WOSA extensions
provide a standard format independent of the data source.
Controls, Engineering, and Manufacturing. Other WOSA extensions are under
development for such diverse areas as control systems, engineering, and
manufacturing.
--
☆ 来源:．BBS 荔园晨风站 bbs.szu.edu.cn．[FROM: bbs@192.168.11.111]
[回到开始]
[上一篇][下一篇]
荔园在线首页 友情链接：深圳大学 深大招生 荔园晨风BBS S-Term软件 网络书店