The geturl documentation claims that, geturl will
return immediatly with a token if the -command option
If geturl can not make the initial socket connection to
a url, it blocks until the timeout expires and calls
the -command proc before geturl has returned a token.
This causes at least the following two problems:
1. The block causes any following geturl calls to hang
before processing. This destroys the asynchronious
2. It invokes the -command proc with a token that is as
yet unknown to the general processing loop.