<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/complement/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/complement/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sun, 29 Sep 2002 10:22:26 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/complement/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>async IO</title><link>https://sourceforge.net/p/complement/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;One should consider sockstream implementation based &lt;br /&gt;
on async io mechanism; &lt;br /&gt;
this mechanism avalable as on modern Linuxes, as on &lt;br /&gt;
Solaris; and on &lt;br /&gt;
Windows we have analogies, based on Windows events. &lt;/p&gt;
&lt;p&gt;Async IO will allow to avoid poll/select calls, and may be &lt;br /&gt;
clean up &lt;br /&gt;
situation with number of bytes available for non-blocking &lt;br /&gt;
read and &lt;br /&gt;
zero on closed socket. &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Petr Ovtchenkov</dc:creator><pubDate>Sun, 29 Sep 2002 10:22:26 -0000</pubDate><guid>https://sourceforge.netb1708171b68f07fecb14283298695015a416a2b4</guid></item></channel></rss>