<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OSI Model on Artur Rios Lab</title><link>https://lab.artur-rios.tech/tags/osi-model/</link><description>Recent content in OSI Model on Artur Rios Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 20 Oct 2026 18:00:00 +0000</lastBuildDate><atom:link href="https://lab.artur-rios.tech/tags/osi-model/index.xml" rel="self" type="application/rss+xml"/><item><title>How Do Computer Networks Work? TCP/IP, the OSI Model and the Protocols Every Programmer Uses</title><link>https://lab.artur-rios.tech/fundamentals/computer-networks/</link><pubDate>Tue, 20 Oct 2026 18:00:00 +0000</pubDate><guid>https://lab.artur-rios.tech/fundamentals/computer-networks/</guid><description>&lt;p&gt;Very few programs work alone. A web page fetches data from an API, the API&#10;queries a database on another machine, the database replicates to a third, and&#10;all of them ask a time server what time it is and a name server where everyone&#10;else lives. Every one of those conversations crosses a network, and every one&#10;of them can be slow, fail halfway or arrive in pieces. A programmer who&#10;understands what happens between &lt;code&gt;connect()&lt;/code&gt; and the reply can tell a DNS&#10;problem from a TLS problem from a congested link, and can write code that&#10;copes with all three.&lt;/p&gt;</description></item></channel></rss>