On Wed, Feb 8, 2012 at 9:37 AM, Free Ekanayaka <[email protected]> wrote: > Hi Nikolaos, > > |--==> On Tue, 7 Feb 2012 13:46:25 -0800 (PST), papagr > <[email protected]> said: > > [...] > p> That's right. A ProjectRepository plays the role of a Context. > p> Unfortunately, I have to work with a legacy SQL database and traversal > p> is not a natural fit. It requires extra coding to setup a custom Root > p> object where Repository instances are registered during startup. > > Yes, there's a bit of overhead, but I think it pays off. I've started > writing a python_contextroutes package that should help with this use > case, if you're interested in it I can send it to you or publish it > somewhere (it's basically done, but lacks documentation and packaging).
What will this contextroutes package do, or what kinds of cases would it be applicable for? I have come up with some cases where I might use a bit of traversal, or traversal after a route (/admin/*traverse), or traversal on a non-URL path specified by the route (traverse=). Where would contextroutes fit into this, or which cases would it be useful in? -- Mike Orr <[email protected]> -- 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.
