scheduler.peer method doesn't timeout

[Oscar Curero]

Hi,

Reading scheduler.peer I read "If all asyncoros are running on a local network, they can find each other automatically through UDP broadcasting. However, asyncoros running at remote network(s) need to be explicitly added with peer method".

That's nice, but what happens if the peer on the remote network can't be reachable because there's a firewall blocking the access? I tested on my own mschine and all I get is a infinite wait. Should scheduler.peer have a timeout (like scheduler.locate has) or is there a way to stop it?

Thanks!
Oscar

[Giridhar Pemmasani]

peer method sets timeout of 2 seconds for sending discovery/ping requests so if the peer can't be contacted, they should timeout. There is no timeout for sending 'stream' request, but that is sent to known (i..e., already communicated) peers. I am guessing the issue may be elsewhere / bug in peer method but not adding timeout, although timeout can be added to sending 'stream' peer request. Can you post example program that shows the issue?