Gregory W. Bond wrote: > thanks for the prompt reply wyatt - alas, two levels of nesting isn't > adequate for my purposes - after looking at the routes documentation, > i see that routes only supports two levels of nesting which is why, i > assume, restler has this constraint - it would seem that generalizing > the routes resource map to handle arbitrary levels of nesting is in > order....
I wonder if something more akin to wsgicollection could work? Or (and this might be vaguely what wsgicollection does) you basically parse off the constructor arguments from the front with Routes, and then leave the remaining bits (PATH_INFO, *path_info in Routes I think) for the controller to interpret internally. -- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org | Write code, do good | http://topp.openplans.org/careers --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
