From: Volkan YAZICI
Subject: Upcoming WAIT-FOR-INPUT-AVAILABLE in usocket
Date: 
Message-ID: <fb67db5c-8a83-4394-bed6-90651c060ad9@v32g2000hsa.googlegroups.com>
Hi,

I thought comp.lang.lisp inhabitants would be interested in this
usocket-devel mailing-list thread[1]:

On Dec 23, 2007 3:12 PM, Erik Huelsmann <········@...> wrote:
>On Dec 22, 2007 9:36 PM, Volkan YAZICI <········@...> wrote:
>> There are lots of messages dropping to comp.lang.lisp and #lisp @
>> irc.freenode.net about how to poll a connection socket. One common
>> advice is to implement it on top of READ-CHAR-NO-HANG with
>> timers. Would anybody consider contributing such a socket polling
>> facility to usocket library? It might not be totally portable across
>> all lisp implementations in the wide, but will probably run on major
>> ones. This will be better than not having any. Any ideas?
>
> Yes! Thanks for mailing. As a matter of fact, the function you
> describe exists in the usocket trunk code: that contains a function
> 'wait-for-input-available' which polls several streams for available
> input at once and allows a time-out to be set.
>
> The facility is even completely portable, with the exception that the
> following implementations aren't implemented yet:
>
> - SBCL, Win32
> - LispWorks, Win32
>
> The feature could use intensive testing and generally 'heavy' use. The
> interface isn't guaranteed to stay the same, but in case it changes,
> the changes will be announced here and won't be far off what it's now.
>
> The reason the code hasn't been released in an official release is
> exactly the reason it's not (yet) implemented on SBCL and LispWorks in
> their Win32 incarnations...
>
> So, if you could promote the code, have people test it and send their
> feedback to this list, we're more likely to see a new usocket release
> with this support soon. (Subscription to the list is not required, but
> non-member posts are subject to moderation.)

I don't have much experience with Common Lisp on Win32, but I thought
others would want to contribute to that code.

[1] http://common-lisp.net/pipermail/usocket-devel/2007-December/000090.html


Regards.