On Fri, Jul 12, 2013 at 4:21 PM, Sam Roberts <[email protected]> wrote:
> Run an http server (express maybe), listen(0), use your web browser to > connect to the single ephemeral port. > > Now cluster it. You have N workers on N different ephemeral port, > meaning you don't have http load balanced across a set of servers > listening on the same port. > > I'm not saying I like that there is no choice about the current > behaviour, and it clearly is a problem for some use cases, but I have > express apps that do exactly the above. > How do they communicate the ephemeral port to whatever needs to connect to it? If you're really talking about simple local apps, where you'd just dump the port to stdout, I don't understand why you'd cluster it. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
