Create a new account

It's simple, and free.

Client/Server "Push" Strategies Summary o

he task is to insert or add an item to a database, for instance, that act is also called "pushing," while if the request is to withdraw an item, that act is called "popping."

It usually falls to the C part of the CS relationship to manage the following:

* Entry data validation (including password control)

* Server program requests dispatching

Sometimes called "front end" applications, client programs comprise everything the user sees.á The chart below shows possible arrangements and architectures, in this case, for a knowledge management (Netscape) model.

The exhibit immediately above shows the multiple variations that could be dealt with in CS architecture.

The other element of the relationship is the server program which is charged with fulfilling the client request by performing the task or tasks requested.á Server programs generally:

*á Receive requests from client programs

*á Execute database retrieval and updates

*á Dispatch responses to client requests.

In two-tier architecture, a client talks directly to a server, with no intervening server.á It is typically used in small environments (less than 50 users).á It is imperative to realize that prototype two-tier design cannot automatically be upgraded by adding more users to the server.

In performing a literature review of the relevant papers and analyses which led to the development of CS, it is essential to consider the many writings of Dr. Vannevar Bush, who, as early as 1945, was suggesting the possibilities and the needs of hyperlinking language and thought.á He first published this concept in 1945 in a widely acclaimed article in Atlantic Monthl

...

< Prev Page 2 of 7 Next >

More on Client/Server "Push" Strategies Summary o...

Loading...
APA     MLA     Chicago
Client/Server "Push" Strategies Summary o. (1969, December 31). In LotsofEssays.com. Retrieved 11:11, May 04, 2024, from https://www.lotsofessays.com/viewpaper/1702214.html