Internet servers clients can become monolithic

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: data – Host business rules – Servers may become overloaded if they need to process both database requests and the business rules. • Internet servers – Clients can become monolithic applications – Respond to client requests for Internet services such as the Web, FTP, or Telnet – Most popular Internet server: HTTP server (Web server) – Examples of HTTP servers: Microsoft’s Internet Information Server, Netscape Enterprise, and Apache. Copyright © 2009-10 Y.M. Cheung, William Tan and Carson Woo – Respond to many concurrent requests initiated by the client applications. – Manage resources required to fulfill the requests. These resources include databases, Web sites, files and printers. Client Two-Tier Architectures: Types of Servers BUSI 335 • Server’s roles: 39 • Three-Tier Architectures – Separate business logic from database and actual data presentation BUSI 335 Copyright © 2009-10 Y.M. Cheung, William Tan and Carson Woo 40 C/S Architectural Styles Presentation Component • Classify C/S systems with respect to the • Presentation logic following components: – format and present data on screen (graphical user interface) – presentation component: how the application is displayed – manage input through mice and keyboards – processing component: how the information entered into the system is verified and processed before it is stored in the database – event monitoring • Presentation logic is always placed on the – storage component: manages data storage and retrieval from physical storage devices BUSI 335 Copyright © 2009-10 Y.M. Cheung, William Tan and Carson Woo client 41 BUSI 335 Three sub-components: • I/O processing logic (typically client-side) • Data manipulation logic – Manages interaction with physical storage devices – data validation and error checking (e.g., input masks) • access tables • business logic (typically client-side) • enforce referential integrity (if possible) – code containing business rules (e.g., “cannot ship more than we have...
View Full Document

This document was uploaded on 03/04/2014 for the course COMM 335 at The University of British Columbia.

Ask a homework question - tutors are online