Please enable JavaScript.
Coggle requires JavaScript to display documents.
Transport Layer TCP/IP - Coggle Diagram
Transport Layer TCP/IP
Identifiers
MAC address
- Data LInk layer
- Used in local network
IP address
- Network Layer
- Identifies the device in the network.
Port
- Transport Layer
- Identifies the process/service inside the device.
Client-server model
Client
- Uses the service
- Starts after server
- Sends the first message
Server
- Offers the service
- Must start first
- Waits in listening mode
Client and server are processes, not just physical machines.
Transport Services
UDP
- Connectionless
- Fast
- SImple
- No guarantee of delivery
- No guarantee of order
- No guarantee against duplicates
UDP can be used with custom reliability mechanisms.
Rare but possible,
TCP
- More managment system
- Connection-oriented
- Reliable
- Ordered
- Error Control
- More expensive in time and resources
-
UDP operation
UDP Server
- Create socket
- COnfigure address and port
- BInd socket
- WAit with recvfrom()
- Respond with sendto()
- Close socket
UDP Client
- Create socket
- Configure server address and port
- Send with sendto()
- Receive with recvfrom()
- Close socket
TCP vs UDP
UDP
- No connection setup
- Faster
- Less overhead
- Used for multimedia, simple requests.
TCP
- Connection setup required
- Slower
- More overhead
- Used when reliability matters
FIle Descriptor?
Small integer number that the operating system uses to identify an open file, socket , pipe, or device for a running process.
-
The network layer gets the packet to the computer.
The transport layer gets the data to the correct process/application.
-
memset --> i HAVE TO CLEAN THE HOUSE,
-