<div dir="ltr">Now that we have found a way to make a Gambit-internal port of OS file descriptors, how about the other way around, i.e.,<br><br>a) How get file descriptor values of active Gambit-internal TCP socket connection ports?<br>
b) Is there a way to make Gambit never make any read operations on a file descriptor / socket? (Currently, I suppose it simply does not, before one invokes a port read procedure from Scheme. Perhaps one would have to tweak the read buffering-related settings on port creation.)<br>
<br>Thanks<br>Mikael<br><br><div class="gmail_quote">2008/9/3 Christian Jaeger <span dir="ltr"><<a href="mailto:christian@pflanze.mine.nu">christian@pflanze.mine.nu</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
P.S. I've now reworded the description in the file a bit to make the intent clearer. I'm attaching the diff and the files here to make sure they stay available in the archive and since the diff would only be seen when actually using the Git checkout.<br>
<br>
Maybe Mikael could confirm some time whether this solution was what he needed and whether it worked.<br><font color="#888888">
<br>
Christian.<br>
<br>
</font></blockquote></div><br></div>