10 ms·
This is awesome. The neat thing is that fitzpatrick will probably be able to actually pull it off. I just hope it'll be able to run Catalyst.
by staunch 18y ago
This is awesome. The neat thing is that fitzpatrick will probably be able to actually pull it off. I just hope it'll be able to run Catalyst.
- hsmyers 18y agoFrom what I've seen on the list, Catalyst seems to be running a little ahead at the moment.
- mst 18y agoWe intend it to. Or, given the timescale, run HTTP::Engine, which is an extraction of the Catalyst::Engine system that's designed to be used by any framework - i.e. to become a perl equivalent to WSGI - and which Catalyst is going to port to once it's baked.
- jrockway 18y agoRunning Catalyst is a goal. If it turns out that we have some time to really make it nice, I'd prefer to support any framework that uses HTTP::Engine. Right now, that's nothing, but since HTTP::Engine is basically extracted from Catalyst, getting Catalyst to run will be easy. But it also means that we'll get other Perl frameworks like CGI::App (they've indicated interest, anyway), Continuity, Jifty (perhaps), etc. The Python guys may be happy with one framework... but this is Perl. There's more than one way to do it :) BTW, I'm a Catalyst core developer, so I'll certainly do everything I can to make working with Catalyst on GAE enjoyable. That's what I want for my applications. But really, getting the web framework to work is the easy part. Getting a Perl that meets Google's requirements is the hard part.