On Tue, Jan 5, 2010 at 11:23 AM, Felix Gilcher <[email protected]> wrote: > Anyways, you can sort of read routes from the database. You can create a > streamwrapper that returns xml code and xinclude that. Stream wappers are > supported in xinclude statements.
Can I ask if you could give an example of how to do this? I can see how to make a stream wrapper http://php.net/manual/en/book.stream.php , but where would I do this in an Agavi project, and how would I xinclude that? > Each and every request, whether it matches or not needs to build the whole > routing tree from the database. Requests that don't match need to go through > all of that. This is a massive overhead, Then would this be an argument to generate the xml "semi" dynamically: generate an xml file when the dynamic routes are created/deleted, and xinclude that file? *Or*, if using the stream-wrapper route, would the generated routing.xml get cached along with all other config? When the dynamic routes are updated, this cache could be cleared. Michal. _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
