[racket-users] Re: set a timeout to tcp-connect

2015-07-17 Thread mazert
Le 17/07/2015 16:16, Matthias Felleisen a écrit : This actually works. But I am not sure why you'd want to do something like that. Ah yes, letrec is what I was looking for :) . The goal was to test a port with a specific timeout (here I set it to two for dev purposes, but 10 is better). I

Re: [racket-users] Re: set a timeout to tcp-connect

2015-07-17 Thread Matthew Flatt
At Fri, 17 Jul 2015 16:58:50 +0200, mazert wrote: Le 17/07/2015 16:16, Matthias Felleisen a écrit : This actually works. But I am not sure why you'd want to do something like that. Ah yes, letrec is what I was looking for :) . The goal was to test a port with a specific timeout (here I

[racket-users] Re: set a timeout to tcp-connect

2015-07-17 Thread mazert
Le 17/07/2015 17:08, Matthew Flatt a écrit : It's possible (but unlikely) for the thread bound to `a` to complete and try to kill `b` before the variable `b` is initialized. Ah ok, yes that is risky in this case, plus we didn't close the tcp connection. Here's what I'd do: * Create a

[racket-users] Re: set a timeout to tcp-connect

2015-07-17 Thread mazert
Le 17/07/2015 17:06, George Neuner a écrit : Won't the connection attempt eventually time out and cause an exception when the TCP stack closes the socket? I know the default connect timeout is rather long though (150 seconds?). Yes it will close for sure but after a long time (maybe 150 sec