in reply to PSGI / Plack
It is Awesomeness™ ... and here’s (I think) why.
For the past five months I’ve been dealing with a legacy application that was “wedged into” the Apache server by means of mod_perl. This made perfect sense in 1998 or so when this system was first put on the drawing board, but it does not make sense now. Plack enabled me to retrofit the application, with only a small number of very targeted changes, to run in FastCGI. Or, in any and every other deployment alternative that Plack supports.
Plack is like a mechanical “slip joint” for web applications. Plack provides a series of server-specific interfaces, all of which support a single, server-independent API. By writing your application in this way, you are able to switch it to many different deployment strategies without re-writing it.
It certainly is convenient that one of those “deployment strategies” is the command-line plackup command. This runs the app on your command-line, and yet your app cannot (unless it wants to...) see the difference. (plackup is “just another Plack-compatible interface.”)
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: PSGI / Plack
by davido (Cardinal) on Aug 17, 2011 at 02:56 UTC | |
by grantm (Parson) on Aug 19, 2011 at 00:55 UTC |