Re: [Myghty-users] resolver proposal - everybody chip in !

[Ben B. <bba...@am...>]

On 4/15/05 7:59 AM, "mike bayer" <mi...@my...> wrote:

> A rough sketch of the one you are looking for is (forgive my paraphrasing
> of the parachute URIs...):
> 
> resolver_strategy = [
> # all subexecs and inherits just resolve to component_root
> Match(context='subrequest,inherit', strategy = [
> # resolve the file
> ResolveFile(),
> 
> # or not found
> NotFound()
> ]),
> 
>         # do that translate path thing you were doing
> PathTranslate(
> (r'/te/article/(.+)' , '/foo/bar/article.myt?id=\1')
> ),
> 
> # resolve your modules
> ResolveModule(
> {r'/te/accounting*' : 'parachute.Accounting'},
> {r'/te/login*' : 'parachute.Login'},
> )
> ]

Actually, since I just want to change the resolver strategy to ResolveFile,
I could leave ResolveModule() to match the current module_components and
just use the Match with context='subrequest,inherit'. This would almost be
ideal, except that this approach appears to be global.

The first proposal allowed resolver strategies to be shifted on the fly by
specifying it as an argument to subexec/redirect. Using this 3rd proposal,
how would I shift the resolver back to checking against module components
from a subexec?