Having worked on load balancers I can say load balancing multiple apps on raw TCP is less than trivial. Basically you end up having to make users declare their socket needs before hand, and you assign a host:port that will map to their app inside the internals of the PaaS. If someone has good ideas on how to make this not painful for users, let me know.
Cheers, Bradley On Tuesday, November 6, 2012 2:50:32 AM UTC-6, paul_tanner wrote: > > Hi, > > We have developed a webserivce built in node that susbcribes to TCP > sockets to get realtime input. > > Having got excited about switching from dedicated severs to PaaS I > seem to have hit a brick wall in that non-http ports are not yet > supported on those I've looked at. > > This is a shame because quite a large class of apps are ruled out > while this restriction remains. > > I hear that websockets will be supported real soon now. This is > goodness but not enough for the above requirement. > > Have I missed anything or will I need to be super-patient on this? > > Regards, Paul > > -- 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
