Lecture 3 – Networks and Distributed Systems. CSE 490h – Introduction to Distributed Computing, Spring 2007. Except as otherwise noted, the content of this presentation is licensed under the Creative Commons Attribution 2.5 License. Outline. Networking Remote Procedure Calls (RPC) Activity
CSE 490h – Introduction to Distributed Computing, Spring 2007
Except as otherwise noted, the content of this presentation is licensed under the Creative Commons Attribution 2.5 License.
The server creates a listener socket attached to a specific port. 80 is the agreed-upon port number for web traffic.
The client-side socket is still connected to a port, but the OS chooses a random unused port number
When the client requests a URL (e.g., “www.google.com”), its OS uses a system called DNS to find its IP address.
Server chooses a randomly-numbered port to handle this particular client
Listener is ready for more incoming connections, while we process the current connection in parallel
Even more low-level protocols handle how data is sent over Ethernet wires, or how bits are sent through the air using 802.11 wireless…
HTTP/1.0 index.html GET
HTTP/1.0 hello.gif GET
foo.dll,bar(4, 10, “hello”)
err: no such function
bar(arg0, arg1); //just write this; calls “stub”
(We’re using the blue cover sheets on the TPS reports now…)
What happens if we write half of a transaction to disk and the power goes out?
Distributed System Design