z-logo
open-access-imgOpen Access
Client/Server Communication Concepts For A Data Communications Course
Author(s) -
S. Ramakrishnan,
Mohammad Dadfar
Publication year - 2020
Publication title -
papers on engineering education repository (american society for engineering education)
Language(s) - English
Resource type - Conference proceedings
DOI - 10.18260/1-2--6454
Subject(s) - computer science , client–server model , suite , client , the internet , fat client , protocol stack , world wide web , session (web analytics) , communications protocol , protocol (science) , server , unix , operating system , computer network , wireless sensor network , medicine , alternative medicine , archaeology , software , pathology , history
As the computing environment is shifting towards client-server computing, there is a vital need for people with expertise in internet applications and network programming. We feel this area will continue to attract more attention in the future. Universities are addressing this need by offering courses in computer networking and data communications. An undergraduate course in data communications appears to be a suitable vehicle for discussing client-server concepts and internet applications due to the direct relationship between clientserver concepts and computer networks. These ideas are often complemented by hands-on experience in writing client-server applications. Traditionally, UNIX machines provide support for process to process communication within the same host by using a BSD protocol stack. The TCP/IP protocol suite is a direct extension of this idea except that it provides for communication between two hosts. In this paper, we propose a project that illustrates the interoperability of these two protocol architectures and the clientserver relationships all in a networked environment. The client and the server reside on two different hosts. The application user is under the illusion that the communication is over the BSD suite of protocols. Basically, we employ a TCP/IP paradigm at the backend of the two hosts, and a BSD stack at the front end of the client, and the server. Thus, communication from the client goes over client-side BSD protocol stack to the server-side BSD protocol stack, via the intermediate TCP/IP protocol stack.

The content you want is available to Zendy users.

Already have an account? Click here to sign in.
Having issues? You can contact us here
Accelerating Research

Address

John Eccles House
Robert Robinson Avenue,
Oxford Science Park, Oxford
OX4 4GP, United Kingdom