+1 On Apr 8, 11:25 am, Jonathan Lundell <jlund...@pobox.com> wrote: > (Context: I've been working on URL parsing.) > > One of the difficulties that parsing web2py URLs presents is that the > boundary between /a/c/f and args isn't explicit, along with the fact that > pieces of /a/c/f can be implied (in particular when routes.py is being used). > > RFC2396 (1998) introduced (or rather extended) the notion of 'parameters', > taking advantage of the fact that ';' is reserved. So the RFC2396 approach is > to write: /a/c/f;parameters?query_string, or in web2py terms /a/c/f;args?vars. > > That is, the boundary between /a/c/f and args is marked with a semi-colon > instead of a slash. Args can of course be further divided however one likes; > vars is subdivided with '&'. > > What I'm working on is an alternative to (or rather extension to) the > routes.py logic that is capable of supporting arbitrary encoding where > appropriate (especially in args and vars) and that does not rely on regexes > to do the work. The present scheme would remain in place. > > Which brings me to my question: I'd like to use the ';' convention to > separate /a/c/f from args in this new regime. Does anyone have any strong > feelings about it one way or the other? > > (One last thing: the architecture would be somewhat modular, so that besides > the current mechanism and the one I'm describing, it would be fairly > straightforward to introduce new ones.)
-- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
