Yep, but there are interesting ways to do things still, like STUN and SOCKS bindings if you have a proxy of your own out there you can generally setup the tunnel inside most PaaS. Generally though the PaaS is stuck to preallocating port/host pairs and charging for them since most don't give you a full fledged IP.
On Wednesday, November 7, 2012 12:27:29 PM UTC-6, Matt Sergeant wrote: > > The problem these PaaS providers face is that http (and even https with > SNI) allow you to route incoming requests by hostname on a single IP > address. > > Other TCP services (generally) do not allow this, forcing the provider to > give you a unique IP address. This is relatively straightforward for > someone like Amazon who have several /15s available to them (131k IP > addresses each), but much more complicated for other PaaS providers. > > On Wed, Nov 7, 2012 at 11:58 AM, Evan <[email protected] <javascript:>>wrote: > >> 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. >> > > -- 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
