On Jan 6, 2011, at 11:52 AM, VP wrote: > > While this is intended to simplify the current specifications of > routes.py (I think), what I have seen is more confusing to me. Does > this replace the old routes.py? > > Maybe, can you provide examples of typical use cases? For example, > one VPS account, each domain mapping to each app. Anything else?
BTW, I'd appreciate if you'd send me (or post here) your existing routes.py. I'll send back (or post) the equivalent routers configuration. I'd like to see some real-world configurations before declaring that the format and logic is final; it's entirely possible that I've missed some needed features.
