On 10/21/06, Ian Bicking <[EMAIL PROTECTED]> wrote: > Using these two variables more complex dispatchers cannot represent the > information they pull out of the request path. This specification > simply defines a place where such dispatchers can put their information: > ``wsgi.url_vars``.
But what is the point? If the receiving application uses the url_vars information, it's tied to the particular dispatcher - so why does this need to be a standard key, rather than just a private convention? If the receiving application wants to remain compatible with generic dispatchers, how can it make use of url_vars? Or, to put it another way, can you provide a realistic example of a *consumer* of the information? Paul. _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com