- From: Martin Duerst <duerst@w3.org>
- Date: Sat, 11 Aug 2001 13:11:17 +0900
- To: Mark Nottingham <mnot@akamai.com>, Aaron Swartz <aswartz@upclink.com>
- Cc: uri@w3.org
Make it an opaque object that you can query with various methods. Python is OO, isn't it? Regards, Martin. At 20:43 01/08/10 -0700, Mark Nottingham wrote: >You remind me - I logged a bug with Python a while back regarding >their urlparse module; it represents a URI as a six-tuple > > ( scheme, authority, path, parameters, query, fragment ) > >As I read 2396, parameters can occur as a suffix to *each* path >segment, not only on the final one. Guido's response was "great! fix >it!", but I haven't had time to make a go of it. > >URI list, is this reading correct? Any opinions as to what data >structure is best to represent a parsed URI with? (I'm thinking just >make it a 5-tuple, taking out 'parameters', and optionally making >'path' a list of 2-tuples, but that's probably not useful in a lot of >scenarios).
Received on Saturday, 11 August 2001 00:12:02 UTC