Page 33 - DCAP408_WEB_PROGRAMMING

Unit 1: Internet Fundamentals

1.10 Web Server Notes

Although technically not a component of Microsoft Speech Server (MSS), a Web server running
Microsoft Internet Information Services (IIS) is an integral part of a complete MSS deployment
scenario. (IIS is included with Microsoft Windows Server 2003 but it must be explicitly installed.
Click Add/Remove Windows Components and select both IIS and ASP.NET.)
The Web server hosts the speech application, including application resources such as prompt
databases and grammar files. It generates the application Web pages that contain HTML, SALT,
and script. A Telephony Application Services SALT interpreter, or a client device with the
Speech Add-in installed, connects to the Web server.
The Web server hosts ASP.NET pages (.aspx) for applications developed using the Microsoft
Speech Application SDK (SASDK), or using ASP.NET Speech Controls.
Speech Application Deployment Service
Speech Application Deployment Service (SADS) provide a way for MSS to manage the deployed
speech application. When installed on the Web server, SADS appears in the Microsoft Management
Console (MMC) snap-in for MSS, providing the ability to add, remove and update deployed applications.
Prompt Database

A prompt database is an application-specific repository of prerecorded sound files used by the
speech output engines of Speech Engine Services. To improve prompt quality, and therefore the
quality of the speech output, application developers may hire a professional to record the
prompts for the database.

Grammar Files

A grammar file contains a structured list of words and phrases that SAPI parses for the Speech
Engine Services speech recognition (SR) engine. Grammars are specific to applications developed
for the Speech Application Platform.

Task Analyze What are the advantages of Web server?

1.11 Client/Server Architecture Model for Web Request

A web is similar to the server in client/server technology. The server, in client/server technology,
usually connects to a database. The client, in client/server technology, makes a data request to
the server, processes the returned data, and presents the result through a graphical user interface.
A web client makes a resource request to the Web server, processes the returned resource, and
presents the result through a graphical user interface.
The difference between a server, in client/server technology, and a Web server seems to be one
accepts requests for data, and the other accepts requests for a resource. The differences are
dramatic, as we look closer.
The server, in client/server technology, is typically a specialized database server. The Microsoft SQL
server product is a good example. A database server receives requests for data from a client through
vendor proprietary network software. It locates the data and returns it. The client applies application
logic to the data, and presents the result through a graphical user interface. This is a “fat client”
because the application logic is in the client. Figure 1.8 illustrates client/server components.

LOVELY PROFESSIONAL UNIVERSITY 27