X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=TODO;h=0e5050db8ed29f6691845d7583be1987e2b686e6;hb=8d3aaa600b7197750929d983da83b487fc56bf55;hp=f8a3d0c28f8d427353b48bec143189dc6f884848;hpb=3be11704b4a92361c6037d56c831230c729244ce;p=catagits%2FCatalyst-Runtime.git diff --git a/TODO b/TODO index f8a3d0c..0e5050d 100644 --- a/TODO +++ b/TODO @@ -28,30 +28,35 @@ http://github.com/willert/catalyst-plugin-log4perl-simple/tree ## PSGI +### To do at release time + + - Release psgi branch of Catalyst-Devel + - Release new Task::Catalyst + ### Blockers - * Add some tests for Catalyst::Test::local_request - * Test all the options work on all of the scripts - * Document how to use your own .psgi (and how you need to do ReverseProxy yourself if you do) - * Document migration for setting engine in setup - * Document migration for setting engine in $ENV - * Fix Catalyst::Engine::PSGI .psgi script and in app root running tests. + * Fix nginx middlewares so that they are generic, or can somehow + be used by people with their own .psgi files + * Fix a sane / nicer way to do custom engines. + + * I've noticed a small difference with Catalyst::Test. The latest stable + version include two headers, 'host' and 'https'. They are missing from + this version - Pedro Melo on list + ^^ Cannot replicate this? Mailed back to ask for tests.. ### Nice to have - * Do we need to do something else about middleware than let the user provide a .psgi? - What about the reverse proxy middleware - * Do we generate a .psgi by default? - * throw out Catalyst::Test's remote_request in favour of - Plack::Test::ExternalServer - * make sure we're running under a server that support psgi.streaming - maybe - just load the BufferedWrite middleware, although that might break things - relying on ->write doing an unbuffered write + * Test/WWW/Mechanize/Catalyst.pm stable throws a deprecation alert when + using Catalyst::Test changes introduced by Cataplack. Suggested fix is + in the repo: http://dev.catalystframework.org/svnweb/Catalyst/revision?rev=14059 + + * Capture arguments that the plack engine component was run with somewhere, + to more easily support custom args from scripts (e.g. Gitalist's + --git_dir) * throw away the restarter and allow using the restarters Plack provides * remove per-request state from the engine instance * be smarter about how we use PSGI - not every response needs to be delayed and streaming - * lighttpd, iis6, and nginx path-info fixers as proper middlewars as part of Plack ## The horrible hack for plugin setup - replacing it: