curl-library
More TODOs
Date: Wed, 21 Apr 2004 16:31:20 +0200
I know very little about automake/configure, so pt. 37 on non-Windows
is not my cup of tea. Not sure if including libidn should be automatic
or added with "--with-libidn".
36 is already done here, but think I'll postpone the patch until 35 is done
(or after 7.11.2 is released).
38 is easy if we can borrow the URL-parser from OpenLDAP src.
Or use Window' native NLS functions; convert to/from native charset
and UTF-8 (to support non-ASCII ldap queries). But I don't know yet
what the RFC says about encodings in LDAP..
More long-term maybe; support SNMP (v1,2c,3) urls the same we support
LDAP. I.e. via some generic dynamic loading of modules to support unknown
protocols. ".curlrc" could have something like:
--scheme-snmpv1 = (parser=???, lib=libnetsnmp.so).
Enough rant...
--- CVS-latest\TODO-RELEASE Wed Apr 21 10:56:02 2004
+++ TODO-RELEASE Wed Apr 21 14:28:08 2004
@@ -21,5 +21,16 @@
Low prio. Seshubabu Pasam works on this.
35. Rearrange lib/hostip.c to reduce the amount of #ifdefs and make it easier
- to follow "the flow".
+ to follow "the flow". Add debug version of getnameinfo().
Medium prio.
+
+36. Add support for a threaded getaddrinfo() on Windows and IPv6 enabled
+ libcurl.
+
+37. Configure option "--with-libidn" to support IDNA (Internationalising
+ Domain Names in Applications). Translate to/from ACE encoded domain
+ names as needed.
+
+38. Make the ldap protocol work with Windows' built-in LDAP-client.
+ I.e. dynamically link to WLDAP32.DLL and add ldap URL parsing
+ (WLDAP32.DLL doesn't have an UTF-8 ldap_url_parse).
(forget about my previous message sent from another email-address)
--gv
Received on 2004-04-21