[Web-SIG] PEP 444 (aka Web3)
and-py at doxdesk.com
Fri Sep 17 18:06:38 CEST 2010
On 09/17/2010 05:42 PM, P.J. Eby wrote:
> do you have an example of what some real-world code is going to *do*
> with this information?
At level 0, the application can't rely on PATH_INFO at all. It can't do
routing without deployment help from rewrites. It may choose to generate
only links in query-string form instead of routed paths.
At level 1, the application can use routing, as long as any strings
inserted into the generated links are slugged down to simple ASCII
(without %2F or control codes).
At level 2, the application can output full Unicode paths, knowing it
will be able to retrieve unmolested non-ASCII path segments for
matching. This is needed for routing Wikipedia-style Unicode URLs (eg.
in IRI form, http://en.wikipedia.org/wiki/日本).
At level 3, the application can put any byte sequence in a path part and
retrieve it without it having been changed. Probably not a good idea for
an application to require this, but it's here for completeness.
mailto:and at doxdesk.com
More information about the Web-SIG