On 19.07.2009, at 20:37, Michal Charemza wrote:
On 19 Jul 2009, at 16:17, David Zülke wrote:I'm thinking about using routing callbacks on an upcoming projects, together with caching. I see at http://www.agavi.org/documentation/tutorial/step4/routing-callbacks.html that onMatched can modify parameters extract to the route. So I have a good understanding of this and caching...- If using such a parameter in the source for a caching group, is thesource taken to be the parameter before or after the modification by the callback?After.So does this mean that onMatched is always called, no matter of the cache settings? In onMatched I was hoping to convert a "nice" product url alias into a product record instance to pass to the action(s). This would require a database query that I was hoping to avoid with some caching. It is possible to both use caching and onMatched in this way, or would I have to forgo using callbacks/onMatched and query the database within the action itself?
You're not supposed to use routing callbacks for this purpose. Use validation instead. The Sample App has an example Product validator that does such a thing.
- David
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
