<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Select on Nikhil&#39;s blog</title>
    <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/select/</link>
    <description>Recent content in Select on Nikhil&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 29 Mar 2017 07:49:03 -0700</lastBuildDate>
    <atom:link href="https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/select/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Canceling socket operations using I/O multiplexing.</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2017/cancellable-select/</link>
      <pubDate>Wed, 29 Mar 2017 07:49:03 -0700</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2017/cancellable-select/</guid>
      <description>I spent the last couple of months diving into networking code at work. This led to some interesting discoveries, including how to allow an in-progress network operation to be canceled on demand. This can be an attempt to establish a connection, or a socket read or write. The standard use case is to allow the user to cancel an operation or to allow a clean shutdown when multiple threads are operating on sockets.</description>
    </item>
  </channel>
</rss>
