From 69e5ff8cf52b728ac91eaff364e5f482841c0d22 Mon Sep 17 00:00:00 2001
From: prince-mahajan <84352887+prince-mahajan@users.noreply.github.com>
Date: Wed, 26 May 2021 15:43:43 -0700
Subject: [PATCH] Update implementation.html

Fixing the link to a cited blog. The existing link now points to a steroid website so need to pull the blog from internet archives.
---
 docs/implementation.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/implementation.html b/docs/implementation.html
index 78e7eb7405e7e..1476c2be52746 100644
--- a/docs/implementation.html
+++ b/docs/implementation.html
@@ -18,7 +18,7 @@
 <script id="implementation-template" type="text/x-handlebars-template">
     <h3 class="anchor-heading"><a id="networklayer" class="anchor-link"></a><a href="#networklayer">5.1 Network Layer</a></h3>
     <p>
-    The network layer is a fairly straight-forward NIO server, and will not be described in great detail. The sendfile implementation is done by giving the <code>MessageSet</code> interface a <code>writeTo</code> method. This allows the file-backed message set to use the more efficient <code>transferTo</code> implementation instead of an in-process buffered write. The threading model is a single acceptor thread and <i>N</i> processor threads which handle a fixed number of connections each. This design has been pretty thoroughly tested <a href="http://sna-projects.com/blog/2009/08/introducing-the-nio-socketserver-implementation">elsewhere</a> and found to be simple to implement and fast. The protocol is kept quite simple to allow for future implementation of clients in other languages.
+    The network layer is a fairly straight-forward NIO server, and will not be described in great detail. The sendfile implementation is done by giving the <code>MessageSet</code> interface a <code>writeTo</code> method. This allows the file-backed message set to use the more efficient <code>transferTo</code> implementation instead of an in-process buffered write. The threading model is a single acceptor thread and <i>N</i> processor threads which handle a fixed number of connections each. This design has been pretty thoroughly tested <a href="https://web.archive.org/web/20120619234320/http://sna-projects.com/blog/2009/08/introducing-the-nio-socketserver-implementation/">elsewhere</a> and found to be simple to implement and fast. The protocol is kept quite simple to allow for future implementation of clients in other languages.
     </p>
     <h3 class="anchor-heading"><a id="messages" class="anchor-link"></a><a href="#messages">5.2 Messages</a></h3>
     <p>