Catalyst has dispatch logic "scattered" everywhere as subroutine attributes. Contrast this with the centralized control in CGI::Application or CGI::Prototype
DBIx::Class coordinates table relations by isolating each table in a package. Contrast this with the single-file centralized modelling in DBIx::DataModel
App::Cmd figures out dispatch logic by looking for Yourapp::Command::* modules and loading them. Contrast this with the centralized, manual listing required in CLI::Framework.
And we have things like HTML::Mason and Template where control is decentralized and placed at the point of effect, in contrast with push-style templating systems which tend to centralize control in a single subroutine.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: decentralized control and coordination
by ww (Archbishop) on Mar 24, 2010 at 20:49 UTC | |
Re: decentralized control and coordination
by IBlowGoatsSucker (Beadle) on Mar 24, 2010 at 22:29 UTC | |
| |
Re: decentralized control and coordination
by jdrago999 (Pilgrim) on Mar 27, 2010 at 18:55 UTC |
Back to
Meditations