Imagine that you are developing an application using TCP as your transport layer protocol. A new version of the protocol is implemented in your operating system that no longer rearranges outof-order data. Must you make any changes to the application to accomodate these changes? If so, what are some specific changes must you make?

Imagine that you are developing an application using TCP as your transport layer protocol. A new version of the protocol is implemented in your operating system that no longer rearranges outof-order data. Must you make any changes to the application to accomodate these changes? If so, what are some specific changes must you make?

Systems Architecture

7th Edition

ISBN:9781305080195

Author:Stephen D. Burd

Publisher:Stephen D. Burd

Chapter13: Internet And Distributed Application Services

Section: Chapter Questions

Problem 15VE

See similar textbooks

Similar questions

Imagine that you are developing an application using TCP as your transport layer protocol. A new version of the protocol is implemented in your operating system that no longer rearranges out-of-order data. Must you make any changes to the application to accommodate these changes? If so, what are some specific changes must you make?
With the help of a neat sketch explain the steps and buffers involved when an application writes to a TCP socket.
Give some reasons why it could be better for an application developer to run the program using the UDP protocol rather than the TCP protocol so that the program can be executed. Is it even remotely possible for a program to have dependable data transfer while it is operating through UDP, even if the application itself is the one doing the transmitting? If so, in what specific ways?
We saw that TCP sockets handle the data sent as a byte stream, but that UDP sockets know message boundaries. What is the benefit and drawback of Byte-oriented API vs the AP's clear recognition and preservation of application-defined message boundaries?
Both TCP and UDP are separate protocols that may be contrasted with one another. Give us an example of two circumstances in which you, as a software architect, might choose to make use of TCP rather than UDP.
For NAT Network Address Translation Scenario: Jenny Bello is a small business owner selling and making customized computer peripherals. She has been finding it difficult to track her sales and inventories, however recently after an expert's advice, she adopted a Point of Sale (PoS) server. So, she can now track her sales and inventories at the store. However, she ran into another issue, the server can only be accessed within the store, because it has been assigned a private IPv4 address, it is not publicly accessible via the Internet. a) Why is not having the PoS server accessible over the Internet a problem for the business? b) What caused this problem? c) Propose a solution for the problem and explain how the solution works.
Are the TCP receive buffer and the client's application buffer same when utilizing HTTP streaming? How do they engage with one another if they don't talk to one another?
We have seen that Internet TCP sockets treat the data being sent as a byte stream but UDP sockets recognize message boundaries. What are one advantage and one disadvantage of byte-oriented API versus having the API explicitly recognize and preserve application-defined message boundaries?
In a TCP data packet, if the sequence number has the value 001111, ACK number has the value 010110 and the urgent pointer has the value 001100 assuming that URG flag is set. What is the last urgent byte in the data section of the packet? All numbers are in binary.
In a TCP client-server application, what is the point of executing the server software before the client programme?
Are the TCP receive buffer and the application buffer on the client exactly the same thing when HTTP streaming is being used? How are they supposed to behave toward one another if they are unable to converse with one another?
TCP Window Flow Control, consider the following: • The MSS Maximum Segment size is 1024 bytes (I kilobyte) • Window size (rwnd) = 4096 bytes • The sendbase is 0000, the segment size is 1024 bytes How many segments can you send (before acknowledgment) then you have to stop, you stop until some ack comes back? What is the sequence number of the third segment?