BIND - sorting of reverse domain.

[Danny Mayer]

At 04:07 PM 7/8/02, D. Stussy wrote:
>Each child zone forms its own tree under its parent zone, where the parent
>zone's child pointer points at the ROOT of the child zone tree.  Similary, 
>each
>RR-set would form whatever structure is appropriate for it (tree or list) 
>under
>the RR pointer.  (The RR-set could get away with a list because many zones 
>have
>relatively few [less than 5] records; the most common being "A", "MX", and
>possibly "A6"/"AAAA" - and where address records are concerned, many are not
>signficantly multihomed).

This shows that you are not paying attention.  BIND needs to be able to handle
the .com zone with multi-million records, DNSSEC which contains at least
of 20 records with just 4 A records, as well as those mom-and-pop zones with
5 records.  Noone cares about the way the records look when written to disk,
they just get read back in again when the server restarts.  How they look are
irrelevant. You haven't even explained why the order on disk is so important
to you, now if they aren't in the order you like, why you can't just write 
a program
to sort them the way you do like.  You are discussing a subject that was
decided on at least 2 years ago. To change it now, you need to demonstrate
that your alternative code is much faster for retrievals than what is currently
being used and that it will be that way under a hugh variety of circumstances
that BIND usually has to operate.

This is not the right place anyway to be discussing this.  It belongs in
bind9-workers.

Danny