[Solar-talk] Re: [Solar-svn] Revision 3037 (a.k.a page black-list)
Paul M Jones
pmjones at paul-m-jones.com
Sat Mar 22 20:16:24 CDT 2008
Hi Antti,
>> For example, say your default is "something", and that the "base"
>> name
>> is disabled. If a request is for "/base/foo/bar", that would then go
>> to "/something/base/foo/bar" and be handled by the "something"
>> _notFound(). That is, the default controller will receive all
>> "disabled" page names as if they were actions on the default
>> controller. (Hope that made sense.)
>>
>> Does that seem like it might give you what you need?
>
> Yes, this is what I was after. Not 100% sure though if turning
> "/base/foo/bar" to "/something/base/foo/bar" would not cause
> "inconveniences".
I don't *think* it will. Let me play it out here, before/after:
Before (or originally): "/base" invokes Solar_App_Base (or
Vendor_App_Base). Bad plan as we all agree. ;-)
After (or the "*new* new" proposal): "/base" becomes "/default/base",
basically getting converted to an action on the default controller.
Hope that helps clarify the tradeoff.
Further thoughts?
-- pmj
More information about the Solar-talk
mailing list