|
Check-in Number:
|
1237 | |
| Date: |
2001-Oct-31 21:07:22 (local)
2001-Oct-31 20:07:22 (UTC) |
| User: | rse |
| Branch: | |
| Comment: |
move two things from TODO to CANDO and describe in detail |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/sa/TODO 1.30 -> 1.31
--- TODO 2001/10/31 19:52:52 1.30
+++ TODO 2001/10/31 20:07:22 1.31
@@ -2,17 +2,27 @@
TODO
----
-- on resolving multiple addresses can be returned (especially
- one IPv4 and one IPv6!) and each one has to be tried on
- socket+connect for instance. What to do? See also
- http://www.v6.wide.ad.jp/Presentations/ai3-penang0010-v6programming/mgp00015.html
-- support for new getaddrinfo and getnameinfo (IPv6!)
- more test cases to cover full API
- more documentation to fully describe API
CANDO
-----
+o Support for newer DNS Resolving Functions.
+
+ In IPv6 land there are usually the newer DNS resolving functions
+ getaddrinfo(3) and getnameinfo(3). Perhaps we should support these in
+ favor of gethostbyname(3) and gethostbyaddr(3) because the chance is
+ higher that they support IPv6 in case we are in IPv6 land.
+
+o DNS Resolving and multiple results.
+
+ On DNS resolving name, multiple result addresses can be returned. Either
+ because of Round-Robin entries, multi-homed hosts or because of hosts
+ talking both IPv4 and IPv6, etc. Each address has to be tried on
+ socket+connect. What to do? For some hints see:
+ http://www.v6.wide.ad.jp/Presentations/ai3-penang0010-v6programming/mgp00015.html
+
o Nagle's Algorithm and Flushing of Output Buffers.
The kernel performs Nagle's Algorithm (see RFC 896 and search for "nagle
|
|
