{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

5- Architectures - 1 Presentation – Many servers(low end...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
Click to edit Master subtitle style 5/7/11 Mobile Application Architectures CSE 390 Fall 2010
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
5/7/11 Client-Server Layers (software) Layers describe the “division of labor” within the application code. The “thinnest” clients have 0 layers. Fat clients have as many as 3 layers. Servers have from 1 to 3 layers. The layers are: 1. Presentation (UI) Business (Logic)
Background image of page 2
5/7/11 Thin clients Less dependent on mobile OS or platform type. Typically use the widely available Wireless Application Protocol (WAP) browser to display web pages (HTML, XML) or WAP pages (WML). 0 Layers of application code. UI, logic, and data access layers are minimal and merged.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
5/7/11 Fat clients Can operate independent of a server connection. Most often use a store and forward approach to data. More dependent on the platform and OS, and not as portable. Often use a 3 layer design to facilitate code reuse and portability. 2 layer designs merge the
Background image of page 4
5/7/11 Client-Server Tiers (hardware) Tiers describe the “division of labor”
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Background image of page 6
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

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

Unformatted text preview: 1. Presentation – Many servers (low end) 2. Application – Fewer servers (midrange) 5/7/11 Security and durability Firewall Firewall Presentatio n Server(s) Application Server(s) Database Server(s) D B Mobil e A three tier architecture providing maximum durability, security, and scalability. DMZ Intranet Zone D B Store and Forward 5/7/11 Tier architectures - pros and cons • 1 tier – Pros: convenient, quick to develop and deploy, cheaper – Cons: less scalable, hard to secure (you have to place the server in the DMZ which exposes the DB to high risk) • 2 tier (merges the presentation and application servers) – Pros: still convenient, but allows for DB 5/7/11 Client connection types • Always connected (browser-type). • Partially connected (app-type). Store and Forward model. • Never connected (not applicable). • Synchronous communication – all data received and stored before server confirms and acknowledges receipt....
View Full Document

  • Fall '11
  • Scarlatos
  • Application server, Client-server, Middleware, Multitier architecture, Wireless Application Protocol, data access layers

{[ snackBarMessage ]}