Network Architecture

Transactions and Sessions
  • Dragan Nikolik

Abstract

The client/server is a networking model and a relationship concept established between two processes or systems running these processes. A client process once initiated by the client system makes a request for a service to be provided by another system, so-called server process. Usually, the server may respond once, presumably providing the results of performing the service or by launching subsequently an “agent” task, which in turn can perform specific actions in order to complete the client’s request.

Keywords

Network Architecture Online Storage Thin Client Common Gateway Interface Client Process 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Bibliography

  1. App servers strategic tool in Web architecture; Mario Morejon; Computer Reseller News, Manhasset; Nov 6, 2000, Iss. 919; pg. 131, 1 pgsGoogle Scholar
  2. Fat network architectures will have a chance to shine—but this isn’t their year; Bob Lewis; InfoWorld, Framingham; Mar 20, 2000; Vol. 22, Iss. 12; pg. 80, 1 pgsGoogle Scholar
  3. Microsoft Protocol Shows Promise; Leverages Existing Web Architecture; Jamie Lewis’, InternetWeek, Manhasset; Mar 6, 2000; pg. PG. 27Google Scholar
  4. In a flood of mail, readers both attack and defend fat-network architectures; Bob Lewis’, InfoWorld, Framingham; Aug 30, 1999; Vol. 21, Iss. 35; pg. 68, 1 pgsGoogle Scholar
  5. On design of a survivable network architecture for dynamic routing: Optimal solution strategy and an efficient heuristic; Ouveysi, Iradj; European Journal of Operational Research, Amsterdam; Aug 16, 1999; Vol. 117, Iss. l;pg. 30, 15 pgsMATHGoogle Scholar
  6. Wideband Network architecture explained; Roger E Billings’, Computer Technology Review, Los Angeles; Apr 1999; Vol. 19, Iss. 4; pg. 22, 1 pgsGoogle Scholar
  7. New Network Architecture; Aviation Week & Space Technology, New York; March 29, 1999; Vol. 150, Iss. 13; pg. 92Google Scholar
  8. Web architectures rule future development; Michael Vizard; InfoWorld, Framingham; Mar 22, 1999; Vol. 21, Iss. 12; pg. 5, 1 pgs Setting Objectives For Web Architectures; InternetWeek Nick Evans; Oct 5, 1998Google Scholar
  9. Switched Services Access Network Architecture; Telecommunications Paul Berkowitz; May 1998Google Scholar
  10. Network architectures and performance; Information Systems Management Sharp, Duane E; Spring 1998Google Scholar
  11. Data Network Handbook: An Interactive Guide to Network Architecture and Operations; Technovation Bailey, Brian; Apr 1998Google Scholar
  12. A second option on network architecture; Public Utilities Fortnightly Chris S King; Feb 1, 1998Google Scholar
  13. Cabletron versus Cisco: Evaluating network architectures; Telecommunications Axner, David; Feb 1997Google Scholar
  14. Paul E. Renaud, Introduction to Client/Server Systems, John Wiley, 1996Google Scholar
  15. Evans et all, Client/Server: A Handbook of Modern Computer Design, Prentice Hall, 1995Google Scholar
  16. Gary Gagliardi, C/S Computing, Prentice Hall, 1994Google Scholar
  17. Butler Report, Client/Server Computing, McGraw-Hill, 1994Google Scholar
  18. Orfali, Harkey, Edwards, Essential Client/Server, John Wiley, 1994Google Scholar
  19. Dawna Travis Dewire, Client/Server Computing, McGraw-Hill, 1993Google Scholar
  20. Pine, B. J., Mass Customisation. Harvard Business School Press, Boston, 1993Google Scholar

Copyright information

© Springer Science+Business Media New York 2003

Authors and Affiliations

  • Dragan Nikolik
    • 1
  1. 1.Maastricht School of ManagementMaastrichtThe Netherlands

Personalised recommendations