- From: Mark Nottingham <mnot@akamai.com>
- Date: Sat, 11 Aug 2001 09:51:31 -0700
- To: Martin Duerst <duerst@w3.org>
- Cc: Aaron Swartz <aswartz@upclink.com>, uri@w3.org
*hits head* Of course. On Sat, Aug 11, 2001 at 01:11:17PM +0900, Martin Duerst wrote: > 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). > -- Mark Nottingham, Research Scientist Akamai Technologies (San Mateo, CA USA)
Received on Saturday, 11 August 2001 12:51:34 UTC