Mariano,

I might have walke into precisely the situation I was describing: maybe the IDE is blocking, not the socket. If so, I still end up wondering why cmd-. is of so little help??

Bill

From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K
Sent: Friday, August 14, 2009 2:27 PM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Question about Socket

Mariano,

Sockets _should not_block the the entire image, but I have just seen it happen with LDAPlayer; I am not yet sure what to make of it. That said, there should be a way to block the UI until something happens, but that should not be done from the sockets layer, as too many things benefit from mutliple conversations happening in the background. On the blocking side, see references to gemstone interfacing, where the server response is integral to the ide responses, so blocking is considered essential.

Bill

From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck
Sent: Friday, August 14, 2009 1:44 PM
To: The general-purpose Squeak developers list; Pharo Development
Subject: [Pharo-project] Question about Socket

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?

Thanks for any light in this field.

Best,

Mariano