[bind10-dev] xfrin (was Re: revised/refactored data source design proposal)

[Michal 'vorner' Vaner]

Hello

On Tue, Jun 07, 2011 at 11:16:39AM +0200, Jelte Jansen wrote:
> I think the way to handle transfers-in are backend-specific, and that xfrin
> should not be aware of the way any specific backend handles this; so it would
> use the Updater classes described here. For ixfr and dynamic dns, these classes
> do need read access to existing data, so for some backends (like in-memory), i'm
> afraid this does mean 'loading' them (or sharing them with auth, if possible).
> Like you, I do think it should update the persistent storage first, then ping
> auth to reload if necessary. But apart from the ping, this updating should be
> done by the backend implementation, not by xfrin itself.

I didn't mean there should be a condition like:
if source = 'in-memory':

But I'd like to create the datasource with a bool parameter „isAuth“. If it
would be, the data would be loaded into memory. If not, the inmemory would play
a role of thin layer on top of the data source it loads from, just forwarding
the queries. This would allow the read access as well. I just don't think
loading the several-gigabyte zone into memory multiple times is acceptable.

With regards

-- 
Anything is possible, unless it's not.

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