... | ... | @@ -53,12 +53,13 @@ Status update 2: |
|
|
* Added FULL update. Both INCREMENTAL and FULL updates are used in ctl to setup/edit zones.
|
|
|
* Added read-only iterators. Editing the zone requires you to first finish old iterator and start a new one afterwards. Writing iterators required either another zone_contents structure with edits or constant index rebuilding. Nowadays hattrie can rebuild indexes automatically when needed which would make these iterators read/write - but I haven't tested this.
|
|
|
* Enhanced API - allows removing whole RRSet of specific type or the whole node.
|
|
|
* Next steps:
|
|
|
* Experiment with integrating apply_ API into zone_update. I have done that in the `zone_update-v2` branch. Tests are looking good, but I'm not 100% sure the approach cannot diverge from the old way of changeset application.
|
|
|
* Integrating apply_ API into zone_update. Removed lots of duplicated code and simplified iterators (and maybe made them read/write, not sure). See !576 for reference.
|
|
|
* This step includes making parts of the apply_* code public.
|
|
|
* Next steps:
|
|
|
* Replace the changeset with a list of changesets. Required for IXFR.
|
|
|
* *WARNING:* IXFR uses the STRICT option with apply_init while DDNS does not. It is required to add similar option to propagate it into zone_update if it is to be integrated into IXFR.
|
|
|
* Of course integration with zone-loading and AXFR still remains on the TODO list.
|
|
|
* Re-think SOA handling in zone_update/changeset/apply_*.
|
|
|
|
|
|
|
|
|
|
... | ... | |