--- Original Message -----
From: "John Stracke" <jstracke(_at_)incentivesystems(_dot_)com>
OK, but that's a really minor win; you're talking about *maybe* a few
hundred extra memory-to-memory copies (for large queries/responses)--and
they're all on the client side (a DNS server with ACE doesn't have to
decode the ACE), so they don't affect scalability of the DNS. That's a
much smaller cost than introducing an incompatible format.
Again you have fallen into the common underestimation of the upgrade work
required for ACE to work perfectly (including display). What I see is that
applications are already having some trouble going from ASCII and local
encoding to UTF. ACE in essence requires the conversion from local encoding
toUTF first and then toACE. I see trouble here...
MSIE have been trying to implement UTF8 for some time now, yet it is still
far from being acceptable. Are we supposing that any vendor or developer
would do much better job if we complicate the task by adding an additiona