not wanting to discourage other authors, but don't you think that the solution posted above is quite heavy and almost a bit black-magical? don't you think it is quite hard to read & relies a bit too heavily on implementation details? when all that this code achieves (assuming it does) is something you are IMHO much better off *avoiding* to do in the first place? see my original response to the OP for considerations about how to avoid the issue of 'cross-calling controller code' altogether.
in short: you shouldn't be doing that, it's not the way to go. calling controller A from controller B is * too hard to do in pylons, * not especially useful, * of doubtful (architectural) merit. you can do what you want without allowing another brittle code beast into your application by doing a simple refatoring of code. maybe you can argue it should be posssible, maybe other frameworks make it painless. but should you resort to throwing a hog like the one posted at this problem? i doubt it. _wolf --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
