I would like to touch the subject of modules once again.
If I understand correctly, the main reason for splitting the dispatcher
was to allow people to use standard dispatcher if they are not going to
use modules. It's perfectly clear and understandable. Now, when it comes
to ModuleDispatcher I would think it's meant for the people wishing to use
modules in their software, right? So why module dispatcher is a hybrid
between these two worlds?
If you use modules then you probably don't keep your default module in
different directories, am I right?
I would rather see a cleaned up version of dispatcher without this magic
special case voodoo of iterating multiple default directiories based on the
module name alone. Do we really need that? I think we can rule out
backwards
compatibility in order to prepare "good code" for the ZF 1.0. For the sake
of
better OO and simplicity.
How about making ModuleDispatcher a strict module dispatcher? I mean to
allow
adding directories only when the module name is directly specified. And as
a
bonus, an ability to specify your own default module name, like it's being
done
now with controller and action names (in standard dispatcher).
Am I alone on this? To all reading this: please, express your support if
you
feel the same.
--
Martel Valgoerad aka Michal Minicki | martel-KmDv4U93n3M@xxxxxxxxxxxxxxxx |
http://aie.pl/martel.asc
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Idleness is not doing nothing. Idleness is being free to do anything."
-- Floyd Dell