Fernan Aguero ✍: > what plack/psgi is and/or why I should care I hear that often, so here's the elevator pitch I'm usually telling to convey the basic idea.
Catalyst is a Web framework that runs on several Web servers. The different parts necessary to make this work are separated out into adapter classes such as Catalyst::Engine::Apache2::MP20. There are quite a number of them. Then framework X comes along and has to implement these adapters suitable for its codebase, too, and so on for every new framework. This repetition is not a good thing, and the frameworks want to get rid of it. The various adapters are written just once, outside of the frameworks, and with a standardised interface. The frameworks now only need exactly one adapter each, adhering to that interface. That interface spec is called PSGI; the implementation is called Plack. Apart from less code for each framework, there is the other advantage that adding support for a new Web server (e.g. Plack::Handler::Mongrel2) automatically enables this Web server for any PSGI-compliant framework. While it has been possible to run Catalyst 5.8 on top of PSGI-enabled Web servers with Catalyst::Engine::PSGI, Catalyst 5.9 goes native and cuts out one layer of indirection. Now that you know that, you should be able to answer the "Question 2" questions yourself.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
