I am sure Kelly is talking about the top level routing to the app and how
to handle that as opposed to the question of internal routing to "screens"
within the app.


Kelly is asking about a mix of both types of routing - External routing
within a reverse-proxy / load-balancer as well as internal routing within
Node's own HTTP service.

How would one configure both so that a broadly-scoped system performs well,
scales well, you don't introduce too many HTTP restarts?

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].