Early binding for proxy port about em-proxy HOT 4 CLOSED

The thin example post is proxying to a local Unix socket.. so the connection time is zero-to-none.

Not sure how well this will work, but give it a try: wrap conn.server call into EM.next_tick {}. In theory, this should allow you to setup the callbacks and accept the connection, but defer the actual connection until next server tick..

If that doesn't work, then it's certainly doable.. but may require modifications to the current proxy code.

from em-proxy.

That worked. There was an additional difficulty needing to only next_tick until the server is up, otherwise I was ending up with an unresponsive system. I don't completely understand why.

I posted a gist in https://gist.github.com/4259205 - I'd really appreciate any comments/suggestions/improvements, maybe there's a cleaner way to achieve this?

I'll close this issue, thanks.

from em-proxy.

Cool. re, gist: looks good.

from em-proxy.

Fyi, if anyone hits this page - I've used this in https://github.com/dblock/heroku-forward - it's a packaged implementation for beating the Heroku 60s boot timeout.

from em-proxy.