<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Networking on Abhishek Shukla</title><link>https://abhishekshukla.dev/tags/networking/</link><description>Recent content in Networking on Abhishek Shukla</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 06 Jul 2026 12:00:00 +0530</lastBuildDate><atom:link href="https://abhishekshukla.dev/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Resilient Networking in Swift: Building a Retry Mechanism</title><link>https://abhishekshukla.dev/blog/retry-logic-networklayer/</link><pubDate>Mon, 06 Jul 2026 12:00:00 +0530</pubDate><guid>https://abhishekshukla.dev/blog/retry-logic-networklayer/</guid><description>&lt;p&gt;Mobile devices are inherently mobile. Your users will walk into elevators, drive through tunnels, and seamlessly hop between Wi-Fi and 5G. Because of this, network requests fail—a lot.&lt;/p&gt;
&lt;p&gt;If your application instantly shows an error alert the millisecond a connection drops, you are providing a poor user experience. Instead, your app should gracefully handle transient network errors behind the scenes.&lt;/p&gt;
&lt;p&gt;This is where a &lt;strong&gt;Retry Mechanism&lt;/strong&gt; comes in. Let’s explore &lt;em&gt;why&lt;/em&gt;, &lt;em&gt;when&lt;/em&gt;, &lt;em&gt;where&lt;/em&gt;, and &lt;em&gt;how&lt;/em&gt; to implement a robust retry strategy using modern Swift Concurrency.&lt;/p&gt;</description></item></channel></rss>