<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>TCP - Tag - HEJTAO</title>
        <link>https://hejtao.netlify.app/tags/tcp/</link>
        <description>TCP - Tag - HEJTAO</description>
        <generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 04 Oct 2019 00:00:00 &#43;0000</lastBuildDate><atom:link href="https://hejtao.netlify.app/tags/tcp/" rel="self" type="application/rss+xml" /><item>
    <title>How TCP starts and close session?</title>
    <link>https://hejtao.netlify.app/posts/cs-tcp/</link>
    <pubDate>Fri, 04 Oct 2019 00:00:00 &#43;0000</pubDate>
    <author>HEJTAO.COM</author>
    <guid>https://hejtao.netlify.app/posts/cs-tcp/</guid>
    <description><![CDATA[Three-way handshake to start a session Four-way handshake to close a session Why termination need four-way? The four-way is actually two pairs of two-way handshakes.
Of course the step 2 and 3 can merge technically like starting session, but not flexible enough as not atomic.
The client request to disconnect its channel does not mean to disconnect the server&rsquo;s channel.]]></description>
</item>
</channel>
</rss>
