I've been looking for a PaaS provider with the same requirements as well, and haven't had much luck. I've tried appFog, Heroku, no.de (when it existed), and Nodejitsu and they all limit you to 1 (randomly assigned) http/s port.
However, it's very easy to get node running on a vanilla Joyent or AWS instance these days, and you can have all the ports you want. I'm currently doing this, and it's really not that hard to manage. @Tomasz - can you talk more about your experiences using Azure? On Tuesday, November 6, 2012 9:34:06 PM UTC-8, Tomasz Janczuk wrote: > > You can listen on a TCP port to process arbitrary (non-HTTP) traffic using > WIndows Azure Cloud Services. There are two varieties: Web Role and Worker > Role. You need Worker Role. You can set up several instances and have > Windows Azure load balance traffic between them. Check out the tutorial at > https://www.windowsazure.com/en-us/develop/nodejs/tutorials/getting-started/ > . > > On Tuesday, November 6, 2012 12:50:32 AM UTC-8, 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
