[Web-SIG] Next steps...

[Stuart Bishop]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 15/11/2003, at 3:21 PM, Bill Janssen wrote:

> Discussion seems to have died down (though I didn't notice any
> consensus about auth toolkits...).  I suggest we review the items on
> the list.  The next logical step would be to elaborate what each list
> item means, in terms of both design and the work estimate.  I know
> that some folks have working code for some of these items.
>
> I'm going to be mainly offline next week, but I'll try to catch up
> the following week.  My list is posted at
>
>   http://www.parc.com/janssen/web-sig/needed.html
>
> Please remind me of things I've missed or gotten wrong.  Thanks!

RFC3490 and RFC3492 support everywhere (Unicode domain names).
httplib already does aparently, but urllib doesn't. encodings.idna
already exists and does all the real work.

Unicode URIs everywhere ( 
http://www.w3.org/International/O-URL-code.html ).
We should be able to do the equivalent of the following:
	urllib.urlretrieve(u'http://my.2\N{CENT SIGN}.net/\N{COPYRIGHT SIGN}')

Digest Auth as a standalone library, as it is more widely adopted 
*outside*
of the HTTP world.

- --  
Stuart Bishop <stuart at stuartbishop.net>
http://www.stuartbishop.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQE/xblxAfqZj7rGN0oRAoecAJ9cTMdt7sWVSvd/POOyr054FVM9rACeOImv
Gsi40HS66ymJ75XUXdf2LL4=
=cyTd
-----END PGP SIGNATURE-----