9.4.10 Client Server Model 9.4.11 Thin vs Thick Client (REST (Database…
9.4.10 Client Server Model
9.4.11 Thin vs Thick Client
Client Server Model:
Client sends a request message to server, server responds to request by replying with a response message to the client
Defines an API( Application Program Interface establishing a full-duplex 'socket' connection between a web browser and a server over TCP/IP. Thus there is a persistent connection between client and server, allowing both parties to send data at any time.
Web CRUD applications
Using REST, these can be mapped to SQL functions:
GET --> SELECT
POST --> INSERT
DELETE --> DELETE
PUT --> UPDATE
Database connected to browser using REST - Representational State Transfer,
which relies on HTTP request methods
talk to server through HTTP
REST API created and run on server,
eg index.html, is run in browser.
Compare JSON (Java script
object notation) with XML.
Easier for a human to read, more compact, easier to create, easier for computers to parse and therefore quicker to parse
A thin client is designed to be especially small so that the bulk of the data processing occurs on the server.
Eg a network computer without a hard disk drive. They act as a simple terminal to the server and require constant communication with the server as well
A thick client (also called a fat client) is one that will perform the bulk of the processing in client/server applications.
Good for applications require multimedia
components or that are bandwidth intensive
as only needs intermittent contact with the server