What a fantastic idea!<p>I would love to know more about the discussions you had with miyagawa, and how the design for this evolved. Anything this elegant must have taken a ton of iterations.<p>Oh, and may I have an invite, please?
We are a Perl shop and this is good new for us - we need PSGI and multiple databases - This _could_ be the step we are looking for to offload our web stack...it is taking too much time to manage all that, rather than getting on with coding!
This entry in their FAQ after the April 21st outage brought a chuckle-<p>Where is DotCloud hosted?<p>DotCloud runs on Amazon EC2. More specifically, we run on the us-east-1 region, across multiple availability zones.
it seems I am not the only to not get the point of PSGI:<p><a href="http://www.modernperlbooks.com/mt/2011/03/why-psgiplack-matters-testing.html#comment-794" rel="nofollow">http://www.modernperlbooks.com/mt/2011/03/why-psgiplack-matt...</a><p>It resumes quite well my opinion and concern regarding the doc.
huh?<p>- No Apache????<p>- why force a rather devish level PSGI module on all web applications????
oh, yeah, you've been advised by the guy who made the port...<p><pre><code> i've been using CGI::Fast under Apache for years and it has been working just PERFECTLY fine.
Do not see the need to change especially when
the PSGI doc is so badly written...
At least the doc states that people who supports mod_perl/CGI::Fast will not see much benefit of switching to PSGI...
</code></pre>
- what is the Perl version?