#683: Deprecate core.use_routing in favor of a routing config parameter
---------------------+------------------------------------------------------
Reporter: david | Owner: david
Type: task | Status: new
Priority: high | Milestone: 1.0
Component: _OTHER_ | Version:
Severity: major | Resolution:
Keywords: | Has_patch: 0
---------------------+------------------------------------------------------
Old description:
> It always runs, anyway. But the actual idea is that you could then switch
> routing off for, say, the CLI context (which means it falls back to
> {{{$argv}}} or whatever instead of using parsing magic), but keep it on
> for web:
> {{{
> <routing class="AgaviConsoleRouting">
> <parameter name="enable">false</parameter>
> </routing>
> }}}
>
> The calls to this would look like the following:
> {{{
> $ro->getParameter('enable', AgaviConfig::get('core.use_routing'));
> }}}
>
> So we have full BC. Maybe even a dedicated method? It's not used outside
> the routing classes, either.
New description:
It always runs, anyway. But the actual idea is that you could then switch
routing off for, say, the CLI context (which means it falls back to
{{{$argv}}} or whatever instead of using parsing magic), but keep it on
for web:
{{{
<routing class="AgaviConsoleRouting">
<parameter name="enabled">false</parameter>
</routing>
}}}
The calls to this would look like the following:
{{{
$ro->getParameter('enabled', AgaviConfig::get('core.use_routing'));
}}}
So we have full BC. Maybe even a dedicated method? It's not used outside
the routing classes, either.
--
Ticket URL: <http://trac.agavi.org/ticket/683#comment:1>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
