psgi | 易学教程

Perl benchmark between FCGI and PSGI

阅读更多关于 Perl benchmark between FCGI and PSGI

问题 What I know about the FCGI protocol is, the first time the application is called, it loads it into memory, run it, return the response to the server, finish the response but does not end the application, it keeps it running in memory, then next requests will use this compiled in memory copy of the application to process the request. Reading about the PSGI protocol, it seems to be working the same way. My question is, is my assumption correct, they are the same regarding the application speed

PSGI: What is it and what's the fuss about?

阅读更多关于 PSGI: What is it and what's the fuss about?

问题 I have been trying to decide if my web project is a candidate for implementation using PSGI, but I don't really see what good it would do for my application at this stage. I don't really understand all the fuss. To me PSGI seems like a framework that provides a common interface between different Apache modules which lets you move your application between them. e.g Easily move your application from running on mod_perl to fastcgi, and provide the application support for running on both options.

Apache-to-PSGI proxy over a Unix domain socket

阅读更多关于 Apache-to-PSGI proxy over a Unix domain socket

问题 We have many (isolated) installations of a PSGI app that run on the same machine and thus require their PSGI servers to run on unique ports. This is less than ideal from a resource/management perspective, but it also requires the (yet-unmeasured and possibly insignificant) "overhead" of TCP/IP when a Unix domain socket would seem to be more obvious choice when running on the same machine. Fortunately, the app works under Plack's HTTP interface (proxied from Apache via mod_proxy's "ProxyPass")

Multilingual PSGI-web deployment

阅读更多关于 Multilingual PSGI-web deployment

问题 I plan develop one web application with PSGI/Plack. (probaly with Dancer, but not decided yet). The applicatiion should be utf8, multilingual (with Locale::Maketext) and (ofc) will contain some statical pages in the given language. My idea is deploy it in different language domains like en.example.com , de.example.com etc. The application itself is simple, mostly will only fill templates with localized texts and some other (light) functionality. What is the best solution to deploying one

How to setup Apache-like name-based virtual hosts with Starman

阅读更多关于 How to setup Apache-like name-based virtual hosts with Starman

问题 In my previous question I asked about a multi-domain solution, but the question was too complex. Now in short: Is it possible to somehow setup name-based virtual hosts with Starman (or with any other pure perl PSGI server) like with Apache's <VirtualHost ...> directive? Or do I need to use Apache to get this kind of functionality? Any idea? 回答1: The middleware is already done in Plack::Builder with Plack::App::URLMap. The pod saying: Mapping URL with host names is also possible, and in that

Deploying Perl Application

阅读更多关于 Deploying Perl Application

问题 What are the best practices for deploying a Perl application? Assume that you are deploying onto a vanilla box with little CPAN module installation. What are the ideal build, deploy methods? Module::Build, ExtUtils::MakeMaker, other? I am looking for some best practice ideas from those who have done this repeatedly for large scale applications. The application is deploying onto a server. It's not CPAN or a script. It's actually a PSGI web application. That is, a ton of Perl packages. I

Deploying Perl Application

阅读更多关于 Deploying Perl Application

What are the best practices for deploying a Perl application? Assume that you are deploying onto a vanilla box with little CPAN module installation. What are the ideal build, deploy methods? Module::Build, ExtUtils::MakeMaker, other? I am looking for some best practice ideas from those who have done this repeatedly for large scale applications. The application is deploying onto a server. It's not CPAN or a script. It's actually a PSGI web application. That is, a ton of Perl packages. I currently have a deployment script that uses Net::SSH::Expect to SSH into new servers, install some tools and

PSGI: What is it and what's the fuss about?

阅读更多关于 PSGI: What is it and what's the fuss about?

I have been trying to decide if my web project is a candidate for implementation using PSGI, but I don't really see what good it would do for my application at this stage. I don't really understand all the fuss. To me PSGI seems like a framework that provides a common interface between different Apache modules which lets you move your application between them. e.g Easily move your application from running on mod_perl to fastcgi, and provide the application support for running on both options. Is that right, or have I missed something? As I and the team I am a part of not only develop the