[gambit-list] Is long poll for activity on external file descriptors without Gambit reading data currently doable, and if so, how?

Mikael More mikael.more at gmail.com
Wed Sep 3 07:15:52 EDT 2008


So this is it, a mechanism that waits for external fd:s? I.e. it adds an
external fd to Gambit's select() call in the Scheduler, and then returns
when there's data (or one can write)?

So for X external fd:s, one spawns X threads and calls port-wait-for-input
with the port as parameter, and the port in turn is the result of fd->port?

Mikael

2008/9/3 Christian Jaeger <christian at pflanze.mine.nu>

> Christian Jaeger wrote:
>
>> Wait, I think I get what you want: you want to block your Gambit thread
>> just as in a read or write operation but not actually carry out any read or
>> write, correct? Just kind of peek-char that doesn't read into a buffer etc.;
>> or basically, you want that this blocks until there is data to be read or
>> there is the possibility to write data (pardon my shell syntax):
>>
>> ({read,write}-subu8vector (u8vector) 0 0 port)
>>
>> That's a question for Marc I guess.
>>
>>
>
> Ok it didn't let me calm so... check out:
>
> http://scheme.mine.nu/gambit/experimental/wait-for-io/
>
> (git clone http://scheme.mine.nu/gambit/experimental/wait-for-io/.git)
>
> Christian.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.iro.umontreal.ca/pipermail/gambit-list/attachments/20080903/0cbbe2c8/attachment.htm>


More information about the Gambit-list mailing list