5 May
2011
5 May
'11
2:43 p.m.
On 05/05/2011 10:40 AM, Daniel-Constantin Mierla wrote:
There is an workaround for your version as well, just copy the content of the branch route in the 'route[xyz] {...}' and then execute route(xyz); in the branch route. Should work, it is the way I have my configs.
That's what I do. But I've never been clear on why this works: doesn't a request route executed from a branch route still have a "branch route" scope? And if not, what is the exact way to foresee the implications of doing certain things that are not allowed in a branch route explicitly in a request route called from a branch route?
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/