Andy Wardley <[EMAIL PROTECTED]> writes:
> Best of all is that the DISPATCH list can be generated at runtime based
> on a particular algorithm (e.g. mapping URL to dispatch lists):
>
> DISPATCH => OpenFrame::Dispatch::URL->new({
> '/search' => [ qw( foo bar baz ) ],
> '/edit' => [ qw( wiz bang waz ) ],
> '/view' => [ qw( crash bang ) ],
> });
I just think that is all backwards.
The URL should point att the template presenting specific
information.
Form data and other feedback from the client should go to the
specified dispatch, independant of the URL.
And the dispatch should normaly not say anything about what template
to bring up. That's for the URL to say.
It's just like HTML och PHP pages. But with the important difference
that the pages only presents requested information. DB operations and
other computations is handled by apointed modules (dispatch).
If the system (core system or dispath) wants to show other
information, it does that by redirecting to that URL.
Why is it that everyone else wants to turn this inside out?
--
/ Jonas - http://jonas.liljegren.org/myself/en/index.html
