It seems to me, that usocket and IOlib are two projects of mostly the same abstraction level, that implement alternative approaches: Lisp-runtime-backed and OS-backed sockets.  And it would be better, if the alternatives both remain.<div>

<br></div><div>Best,</div><div>Vsevolod<br>
<br><br><div class="gmail_quote">On Mon, Oct 4, 2010 at 4:07 PM, Hans Hübner <span dir="ltr">&lt;<a href="mailto:hans.huebner@gmail.com">hans.huebner@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

On Mon, Oct 4, 2010 at 15:01, Chun Tian &lt;<a href="mailto:binghe.lisp@gmail.com">binghe.lisp@gmail.com</a>&gt; wrote:<br>
&gt; I&#39;m thinking of writing a IOlib backend for USOCKET.  [...]<br>
<div class="im"><br>
&gt; Will this idea be helpful for any USOCKET user?<br>
<br>
</div>It will not be helpful to me at the moment, but I do like the idea -<br>
It would be particularily nice if it would be easily possible to use<br>
USOCKET and still use the I/O multiplexing facility of IOlib (i.e. run<br>
some USOCKET based libraries and add more file descriptors to the I/O<br>
multiplexer without having to resort to threads).<br>
<br>
-Hans<br>
<br>
_______________________________________________<br>
usocket-devel mailing list<br>
<a href="mailto:usocket-devel@common-lisp.net">usocket-devel@common-lisp.net</a><br>
<a href="http://common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel" target="_blank">http://common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel</a><br>
</blockquote></div><br></div>