Advance Computer Networks
1. Concepts of Servers and Clients
1.1. Explain client and server environment and the
communication between clients and servers.
The client-server paradigm is a networked computer architecture in which
clients demand resources or services from servers. Clients begin
interacting with servers, that await responses (Jain et al., 2024). The
means of interaction is often based on a request-response system.
Clients
Systems or apps which require services or resources (Sun et al., 2024). For
instance, online internet browsers, clients for email, and applications for
smartphones and tablets.
Servers
Strong devices or programs that meet customer requirements (Sinha,
1992). Such as the web, the database, email, and storage servers.
Communications
Connection: Clients connect to the server via protocols such as
TCP/IP or HTTP (Xue and Zhu, 2009).
Request: Clients submit their requests to the server.
Processing: The system that handles the request.
Response: The server provides the proper answer to the client.
Protocols
TCP / IP: TCP/IP is a protocol aimed at connecting devices that
creates and sustains connections, decides how to divide data into
messages, and transmits and receives information from the
network layer (Hussam, 2014).
HTTP: Hypertext Transfer Protocol is the protocol used by internet
browsers to connect with web servers.
FTP: File Transfer Protocol.
SMTP: Simple Mail Transfer Protocol.
DNS: Domain Name System.
SSL: SSL means Secure Sockets Layer.
TLS: Transport Layer Security.
Benefits
Scalability: Resources and services may be dispersed over a
network of devices, making them accessible from everywhere.
Data protection: Information may be stored in a single location,
which makes it quicker to safeguard it and handle user permission
and identification.
Load balance: Client queries can be split over numerous servers
to avoid congestion. For instance, e-mail, network printing, the
internet, sharing of files, and database management systems.
The client applies, and the server responds. The sending and receiving of
packets exemplify communication between processes. For communication
, 1.2. Define the terms: Process ID (PID), Parent process
ID (PPID) and ‘init’.
Process ID (PID)
An identification number assigned to every job operating in the kernel
(Zhao et al., 2024). Process IDs begin with 1, which is allocated to
systemd, or init on earlier Linux editions. Process IDs assist to identify
among simultaneous procedures, making it simpler to handle and split
resources.
In the Linux operating system, every task is given a distinctive Process ID
(PID) that acts as its identification (Kim, Kim and Han, 2024). Furthermore,
every program, the init procedure with PID 1, has an underlying process
from which it originates.
Parent Process ID (PPID)
The identification number of the process that initiated another task
(Daghmehchi Firoozjaei, Samet and Ghorbani, 2024). When a software
initiates a multitasking sequence, the procedure that generates the fresh
processes is known as the parent process, while the new procedures are
known as the child processes. The child processes use unique Process IDs
from the parent process. When a child process is formed, it is assigned a
Parent Process ID. For instance, the init process's Parent Process ID (PPID)
is 0, indicating that it has no parent.
The Parent Process ID (PPID) may be a helpful instrument for diagnosing
procedures within Linux system administration (Alqahtani, Almutairi and
Sheldon, 2024). It offers data on the structural connection among
procedures, allowing admins to comprehend process dependency issues,
identify the cause of problems, and stop troublesome programs.
Init
The init function usually utilizes a Proces ID of one (He and Li, 2024). In
Linux kernels 3.4 and later, the init procedure is no more referred to as
"init".
1.3. Compare the operation of parent processes and
child processes.
Table 1: Operational Comparison of Parent and Child Processes
Differential Parent Processes Child Processes
Factors
Create They use system calls to make These processes are created by
child processes fork () in parent processes and inherit all the
(Unix/Linux) or CreateProcess() in attributes from the parent
(Windows) (Kappes and processes.
Anastasiadis, 2024).
Control They can control the child These processes run at their own
processes, they can terminate the and do not bother, interrupt and
child processes, send them control the parent process for their
signals and wait for their execution and running but once they
completion. terminate, they notify the parent
processes.
Resource The resources which can be They firstly share their resources
Allocation shared are memory, files, and with the parent processes, but they
descriptors which can be handles also have their own independent
1. Concepts of Servers and Clients
1.1. Explain client and server environment and the
communication between clients and servers.
The client-server paradigm is a networked computer architecture in which
clients demand resources or services from servers. Clients begin
interacting with servers, that await responses (Jain et al., 2024). The
means of interaction is often based on a request-response system.
Clients
Systems or apps which require services or resources (Sun et al., 2024). For
instance, online internet browsers, clients for email, and applications for
smartphones and tablets.
Servers
Strong devices or programs that meet customer requirements (Sinha,
1992). Such as the web, the database, email, and storage servers.
Communications
Connection: Clients connect to the server via protocols such as
TCP/IP or HTTP (Xue and Zhu, 2009).
Request: Clients submit their requests to the server.
Processing: The system that handles the request.
Response: The server provides the proper answer to the client.
Protocols
TCP / IP: TCP/IP is a protocol aimed at connecting devices that
creates and sustains connections, decides how to divide data into
messages, and transmits and receives information from the
network layer (Hussam, 2014).
HTTP: Hypertext Transfer Protocol is the protocol used by internet
browsers to connect with web servers.
FTP: File Transfer Protocol.
SMTP: Simple Mail Transfer Protocol.
DNS: Domain Name System.
SSL: SSL means Secure Sockets Layer.
TLS: Transport Layer Security.
Benefits
Scalability: Resources and services may be dispersed over a
network of devices, making them accessible from everywhere.
Data protection: Information may be stored in a single location,
which makes it quicker to safeguard it and handle user permission
and identification.
Load balance: Client queries can be split over numerous servers
to avoid congestion. For instance, e-mail, network printing, the
internet, sharing of files, and database management systems.
The client applies, and the server responds. The sending and receiving of
packets exemplify communication between processes. For communication
, 1.2. Define the terms: Process ID (PID), Parent process
ID (PPID) and ‘init’.
Process ID (PID)
An identification number assigned to every job operating in the kernel
(Zhao et al., 2024). Process IDs begin with 1, which is allocated to
systemd, or init on earlier Linux editions. Process IDs assist to identify
among simultaneous procedures, making it simpler to handle and split
resources.
In the Linux operating system, every task is given a distinctive Process ID
(PID) that acts as its identification (Kim, Kim and Han, 2024). Furthermore,
every program, the init procedure with PID 1, has an underlying process
from which it originates.
Parent Process ID (PPID)
The identification number of the process that initiated another task
(Daghmehchi Firoozjaei, Samet and Ghorbani, 2024). When a software
initiates a multitasking sequence, the procedure that generates the fresh
processes is known as the parent process, while the new procedures are
known as the child processes. The child processes use unique Process IDs
from the parent process. When a child process is formed, it is assigned a
Parent Process ID. For instance, the init process's Parent Process ID (PPID)
is 0, indicating that it has no parent.
The Parent Process ID (PPID) may be a helpful instrument for diagnosing
procedures within Linux system administration (Alqahtani, Almutairi and
Sheldon, 2024). It offers data on the structural connection among
procedures, allowing admins to comprehend process dependency issues,
identify the cause of problems, and stop troublesome programs.
Init
The init function usually utilizes a Proces ID of one (He and Li, 2024). In
Linux kernels 3.4 and later, the init procedure is no more referred to as
"init".
1.3. Compare the operation of parent processes and
child processes.
Table 1: Operational Comparison of Parent and Child Processes
Differential Parent Processes Child Processes
Factors
Create They use system calls to make These processes are created by
child processes fork () in parent processes and inherit all the
(Unix/Linux) or CreateProcess() in attributes from the parent
(Windows) (Kappes and processes.
Anastasiadis, 2024).
Control They can control the child These processes run at their own
processes, they can terminate the and do not bother, interrupt and
child processes, send them control the parent process for their
signals and wait for their execution and running but once they
completion. terminate, they notify the parent
processes.
Resource The resources which can be They firstly share their resources
Allocation shared are memory, files, and with the parent processes, but they
descriptors which can be handles also have their own independent
