On Fri, May 07, 2004 at 11:28:50AM -0700, Justin Mason wrote: > I'm assuming that, like an encoded URL, it should dupe to both an > @ version and an undecoded version.
Hrm. Ok. We should probably do full decoding first then, add that to
the queue, then remove the username part and add that to the queue.
My original idea was that we'd have just the raw and "cooked" URIs
returned, and leave everything else up to calling functions. But I can
see the argument about the username bit.
> sure, hack away ;) looks likely to be better alright.
I'll do a few timings and see what falls out. :) It's not like this
function is going to be called a lot, but ... ;)
--
Randomly Generated Tagline:
"Fruit, what's that?
It's a thing you eat when you feel like you need to have fruit."
- Dave McClelland and Chris Smith
pgptm1n9vRJ5E.pgp
Description: PGP signature
