<br><br><div class="gmail_quote">On Fri, Aug 14, 2009 at 3:49 PM, Andreas Raab <span dir="ltr"><<a href="mailto:andreas.raab@gmx.de">andreas.raab@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Mariano Martinez Peck wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi folks: I am preparing my SqueakDBX talk for ESUG and I am doing some comparisons between a database driver with an external library trough FFI and a native driver. I know FFI locks the VM until the function it is being invoked, finishes. But I don't know what happens with Sockets. Do sockets lock the hole VM until you obtain a response?<br>
</blockquote>
<br></div>
The socket interfaces are entirely asynchronous, i.e., there is no blocking. Sockets have semaphores associated with them that are signaled when anything interesting is happening. Check out methods like Socket>>sendData: to see how this stuff works together.</blockquote>
<div><br>Good news then. Thanks for the explanation Andreas.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Cheers,<br><font color="#888888">
- Andreas<br>
<br>
</font></blockquote></div><br>