[bind10-dev] Snapshot of #2377

[Michal 'vorner' Vaner]

Hello

Since so many things are blocked on the #2377 ticket, I brought it to a
half-usable state that could be used as a base for other work. It is in in
trac2377-partial branch (I may push something that doesn't compile on top of
ordinary trac2377, or I could decide to rewrite the newer commits once I write
them).

It is based on merge of snapshots of #2506 and #2382. Well, the history will
look like, but what can we do if we don't want to wait.

It parses some master files, but there are many gaps still:
 • Error handling is missing.
 • Further tests need to be created.
 • There are many TODOs in the code and the current code inside could still
   change a lot (but I think the interface will stay).
 • There's no flexibility in the format ‒ it requires the input to be in form:
     <name> <TTL> <class> <type> <rdata>
   I need to read the ticket description to know how much of the flexibility
   would go into this ticket, though.

And, a question. As I decided to produce separate RRs (see discussion of the
ticket in trac), we need a collector to put RRs together to RRsets. But I'm not
sure how fast we need that. It could be started right away (as it depends on
nothing), but maybe we don't need it, because our data sources will be able to
handle it themself (databases do already and the in-memory needs to be made so
anyway). Should we create a ticket right away and put into next sprint, or is it
OK to wait?

With regards

-- 
Work with computer has 2 phases. First, computer waits for the user to tell it what 
to do, then the user waits for the computer to do it. Therefore, computer work 
consists mostly of waiting.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20121203/5298a9a2/attachment.bin>