FWIW, I preferred your earlier suggestion of Fallback[Handler|
Action].
If this mirrors the behavior of Action (in the way variables are
presented
to the fallback resource) then FallbackAction makes the most sense.
If it is restricted to a filespec at the same dir level, then perhaps
FallbackFilename makes the most sense. (If it can be at the same
level
or in another path, FallbackFile or FallbackResource might be better).
Rich? Pipe up - you know we programmers are useless for naming
things.
You make short, sweet and to the point choices. E.g., ponies.
FallbackHandler sounds good to me. I can't say I'm particularly
concerned about the name, as long as the functionality does what we
want, but FallbackHandler makes a lot of sense.
Sorry for the delay.
--
Rich Bowen
[email protected]
