Utada at The Fillmore
I’m now in Orlando, Florida attending “Perl Oasis” Orlando Perl Workshop 2010.
**Short answer if you come from Google: **Plack is a toolkit containing middleware, helpers and web server adapters to run PSGI. Plack is NOT a web server but it’s rather a “web server interface” which means if you want to run you PSGI application on any web servers, look at Plack to find handlers.
It’s been a week break since I finished the very well received Plack Advent Calendar. And today i’m back on track on Plack development to get ready for the next week Perl Oasis in Orlando.
via www.flickr.com
via www.flickr.com
via www.flickr.com
So, Plack::Request is probably the most useful class/utility in the Plack/PSGI ecosystem but at the same time confuses people to think that Plack is more of a framework or a library for *end users *rather than for an application framework developer.
So I blogged why params() sucks but there’re already applications and libraries that do this: Catalyst and CGI::Deurl for instance. Changing the behavior of these libraries or core framework would break the existing code, even worse, mostly silently (because ref $params->{foo} eq 'ARRAY' would silently return false).
In a typical web application the most frequently occurring task is to get parameters from a request. Perl community and popular frameworks have been having two interfaces to this: param() and parameters(). And there’s a few issues.
via www.flickr.com
During it, he commented “while I was on the plane from San Francisco to Japan I hacked on …”, and then “while I was on the plane here I hacked on …”, and I wondered what is the carbon footprint of miyagawa’s modules?
via www.slideshare.net
via www.youtube.com
via www.flickr.com
via vimeo.com
Something I’ve been thinking of implementing myself, but i have other exciting things to work on these days, so I just free up this idea to the lazyweb:
via vimeo.com
Just a note for myself, but could be useful: