TF_RequestLease() takes long time when saved server is down or incorrect

When testing, I'm finding that if I save a fake address with TF_SaveServer() or if the address is valid, but down, that when I call TF_RequestLease() the response takes quite a bit of timein some cases up to a 1.5 minutes. Is there any way to speed that up or is that just the nature of the call?

Thanks,Arie

It depends on the nature of the address. It tries to resolve every address (even fake ones). And if the address is real, and it's accepting connections then it will take especially long.

In TF 4.0 we've added a 20 second timeout so if a user enters a wrong address that dumbly listens to all connections, then TF will just kill the connection after 20 seconds.

So there is a difference between a machine that is up and accepting connection but with TFS down, and an address that doesn't even resolve?

Why not let the user determine how long the timeout should be?

We've considered it. It won't be in the TF 4.0 release.