.learn() - page 6
what I have learned so far
-
Vanilla Seq2Seq - the architecture that leaned on one final state
To understand the basic Seq2Seq architecture you first have to accept one fact: the input is compressed into a single vector. How everything ends up in the last hidden state, and the fundamental limits that follow.
-
Putting it together - what happens when you type a URL
From pressing Enter to the page appearing, every layer in the series is called on within a second. The final part traces all five as a single flow.
-
The application layer (DNS/HTTP) - look up a name, then talk
People use names, not IP addresses. DNS, the distributed system that turns names into addresses, and HTTP, the language the web speaks over them.
-
The transport layer (TCP/UDP) - reliability is a choice
Who guarantees the reliability IP never promised? Ports that distinguish processes, TCP which builds reliability on top, and UDP which refuses to pay for it.
-
The internet layer (IP) - finding the way by address
How do you cross many networks to reach a destination host? IP as a hierarchical address, routing that picks the next step at every hop, and the best-effort design that promises no delivery.