[cgiapp] Re: feedback on CGI::Application::Dispatch

["Viacheslav Sheveliov" <suppressed>]

"Mark Stosberg" <suppressed>
ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ:
news:suppressed
>I just tried out the developer release of CGI::Application::Dispatch
> 2.00, and I have to say I really like it.  It helped me to create
> shorter, cleaner, URLs for my project, pulling together a larger
> dynamic website in something more friendly.
...skipped...

Sounds tasty, but IMHO writing dispatch table in startup script is not very
scalable way.

Lets say we have 10 modules * 10 runmodes. It's 100 dispatch table entries.
Furthermore, installing/uninstalling new modules now is more painfull
procedure.

I think the best way - determining in dispatcher only module name and
runmode. Remaining part of PATH_INFO should be parsed by module itself,
cause it greatly depends on module logic.

Or we can determine dispatch table in module to be called. In dispatcher we
know module name and can retrieve dispatch table as $Module::DISPATCH_TABLE
or $Module->dispatch_table().


Of cause, for simple CGI apps or for fixed core modules it's OK to use
hardcoded dispatch table.

What do you think?





---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed