[gambit-list] open-tcp-client problem?

[Francois Magnan]

Hi,

Ok, this is a nice feature but it could be implemented by the  
programmer using threads . If I want a sequential behavior I will  
have to loop by catching connections errors until the connection is  
completed. The loop will also have to distinguish between real  
connection errors and "still not connected" errors. This is a little  
odd to me but I can write such a function.

Thanks,
Francois Magnan


On 05-08-09, at 09:13, feeley at iro.umontreal.ca wrote:

>> Hi,
>>
>> I have some difficulties using the open-tcp-client primitive on
>> MacOSX 10.4 with Gambit-Cb14. The primitive returns a port before
>> that port is actually ready to be used for sending/receiving data.
>>
>
> Is this a problem?  The Gambit runtime performs an asynchronous  
> connect.
> This is done so that multiple connections can be started in  
> parallel.  If
> there is a connection error it will be reported the next time you  
> do I/O
> on that port.
>
> Marc
>
>