Post 1:

1. Alice has a video clip that Bob is interested in getting. This scenario requires a persistent HTTP connection to exchange the information from Alice to Bob.
2. Bob has another video clip that Alice is interested in getting. In order to get this clip, he needs to utilize the cookies that will be saved on the proxy servers.
3. Bobs web cage creation is a good idea. The HTTP server is a great way to store valuable information like recent requests and responses.
4. Alice can get the video clip using FTP or Email. I believe the most efficient protocol is the File Transfer Protocol. This protocol provides the ability for a client to retrieve a file from the server. In this type of connection, “the control connection remains open all the time, but the data connection id opened and closed repeatedly.” (Forouzan & Fegan, 2007)
5. After making a connection with Alice, Bob can send an HTTP request utilizing a persistent connection. In combination with this request and acknowledgement, the system can utilize the already established connection and the cookies that were created and used. Bob can use the same protocol to get the clip from Alice.
6. There can be an “end of file marker” (Forouzan & Fegan, 2007) after the last response message that lets you know there are no more headers, and the body of the message is next.
7. In a non-persistent connection, the connection must be opened and closed N+1 times. This “N+1”correlates to the number of links and the initial request. Once this number of loops or iterations is complete the connection can be terminated.

This topic reminds me of John 6:44. The bible says, “No man can come to me, except the Father which hath sent me”. This verse tells me that anyone can approach but if you don’t have cookies to prove you’ve been engaged with these protocols or history then you may not approach.

Forouzan, B. A., & Fegan, S. C. (2007). 22.2.1. In Data Communications and networking (fifth, pp. 676–676). essay, McGraw-Hill Higher Education.

The Disciple, J. (2011). John 6:44. John 6:44 KJV – – Bible Gateway. Retrieved April 14, 2022, from https://www.biblegateway.com/passage/?search=john%…

Katz, E. D., Butler, M., & McGrath, R. (1994). JavaScript needs to be enabled for this application to run correctly. Elsevier Enhanced Reader. Retrieved April 14, 2022, from https://reader.elsevier.com/reader/sd/pii/01697552…

Post 2:

In the event that Alice and Bob want to transfer clips over the internet, there are a whole host of ways that this particular task can be accomplished. The one that will be covered in this scenario is to set up a webpage on an HTTP server in order for the parties to be able to upload or transfer videos between themselves. This method is a very simple method and can be done with a few commands in your Linux terminal. On this web page, there are two main protocols that talk to each other during the communication between the machines and the web servers. Those protocols are HTTP or Hypertext transfer protocol and TCP also known as the Transmission control protocol. HTTP is a very well-known and widely used protocol “hypertext transfer protocol (HTTP) is responsible for nearly 10% of the traffic volume on the Internet.”(Gou, 2017)

1. When an HTTP server receives a request message from an HTTP client, how does the server know when all headers have arrived and the body of the message is to follow?

The first thing that happens when a machine connects to a website is that a connection needs to be established. This request from a client means that the machine needs to connect to the HTTP server that is running on port 80 in order to begin accessing the page. Simply attempting to access a web page results in a chain reaction in the network as described in by Phd Tao Zhang,” After receiving an HTTP request message from end-user, the Web server in the data center, which provides resources such as HTML files and other content, or performs other functions on behalf of the client, returns HTTP response to the end-user”(Zhang, 2017). All of this initiation is done through a TCP connection, which is a reliable way for machines to communicate while also mitigating the data lost in transport.

The primary way that servers identify if all the information that’s needed is there, is by the structure of the header and body massage. The request that is sent off by a client should contain blank spaces within the Http request at both the start and end of it. This will then let the server know that the message is complete and that there is nothing left for it to receive from the client.

2. In a non-persistent HTTP connection, how can HTTP inform the TCP protocol that the end of the message has been reached?

In the event that a nonpersistent connection is achieved that simply means that the TCP protocol must continue to reinitiate after termination. In this case, the machine after request and response must start the process over. If that machine is looking to send another request to the server it must reestablish that TCP connects before sending an HTTP request.

Biblical integration

In this discussion topic communication between two machines or entities played a major role. In my mind, this closely reminded me of the importance of prayer.

“In these days he went out to the mountain to pray, and all night he continued in prayer to God.”(Luke 6:12)

When we pray we are making a connection with God, oftentimes in prayer, we are sending God a request. This request could be anything from his protection, love, or forgiveness. God oftentimes will respond to these prayers in some form or fashion, which may not always be obvious. This is similar to the HTTP request and response in a way, because just like HTTP is one way that machines communicate between each other and networks, we communicate with God through prayer.

References

King James Bible. (2008). Oxford University Press. (Original work published 1769)

Gou, G., Bai, Q., Xiong, G., & Li, Z. (2017). Discovering abnormal behaviors via HTTP header fields measurement. Concurrency and Computation, 29(20), n/a.

Zhang, T., Wang, J., Huang, J., Chen, J., Pan, Y., & Min, G. (2017). Tuning the aggressive TCP behavior for highly concurrent HTTP connections in intra-datacenter. IEEE/ACM Transactions on Networking, 25(6), 3808-3822.