On 24.04.2009, at 22:45, PJ Hinton wrote:
When the route is accessed by the first approach described above, things are fine. In the second case, any route that uses a user source does not match. This is because the global filter authentication executes after the route has been determined, and the sources are determined as part of the context initialization.The best idea that we've been able to come up with so far is to move the authentication code into a custom subclass of AgaviWebRouting. Any thoughts on a Better Way (tm) to do this?
Hi PJ, as Veikko said, User::startup() looks to be just the place to do that! Cheers, David
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
