CGI::Application::Dispatch::Server was released in Summer of '07, in part
because CGI::Application::Server didn't have dispatching support.
But soon after, in the fall, CGI::Application::Server was released, which
supports both dispatched and regular CGI::App entry points.
In reviewing the
Mark,
CGI::Application::Dispatch::Server was released in Summer of '07, in part
because CGI::Application::Server didn't have dispatching support.
But soon after, in the fall, CGI::Application::Server was released, which
supports both dispatched and regular CGI::App entry points.
In reviewing
Bradley C Bailey wrote:
In
CAD::Server it tries to serve files staticly first before sending to
dispatch. I think the best solution would be to specify a way to mark
an entry point in the CA::Server config to specify static content.
This would also improve performance since static content
* Michael Peters [EMAIL PROTECTED] [2008-09-17T12:37:04]
Bradley C Bailey wrote:
In CAD::Server it tries to serve files staticly first before sending to
dispatch. I think the best solution would be to specify a way to mark an
entry point in the CA::Server config to specify static content.
Bradley C Bailey writes:
Mark,
CGI::Application::Dispatch::Server was released in Summer of '07, in part
because CGI::Application::Server didn't have dispatching support.
But soon after, in the fall, CGI::Application::Server was released, which
supports both dispatched and
Patches welcome.
I'd like to provide feedback on various proposed changes to
CGI::Application::Server
Need a way to specify parameters to dispatch()
I disagree. The recommended way to do this to define a 'dispatch_args'
routine in your CGI::Application::Dispatch subclass. I think George
* Mark Stosberg [EMAIL PROTECTED] [2008-09-17T20:57:37]
::Dispatch::Server prefers static files first, ::Server prefers dispatching
first
I think it is a bug in ::Server that it prefers dispatching server. The
recommended use of ::Dispatch, and also for Drupal, is to use a rewrite
rule
