There is a problem with relying on setImmediate() in your channel implementation: 1. httpGet... 2. setImmediate() in a tight loop using 100% CPU until httpGet

There is a problem with relying on setImmediate() in your channel implementation: 1. httpGet... 2. setImmediate() in a tight loop using 100% CPU until httpGet() returns ... I'd rather not burn ~100% CPU for what could be a couple of seconds waiting for a slow web server (even if we're nicely burning it).