Colin Vidal
02482d88ba
Use isc_buffer_t for read/write ops
...
To support materialization, each value stored inside cfgmgr must have an
extra flag telling in which mode the value was inserted/updated (i.e.
was it in builtin mode, user mode or running mode).
Instead of playing with pointers arithmetic to squeeze this extra info
in the value being serialized/deserialized into LMDB, uses isc_buffer_t.
2025-02-24 10:35:39 +01:00
..
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-24 10:35:39 +01:00
2025-02-22 16:19:00 +01:00
2022-12-20 21:24:45 +02:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2024-08-15 10:05:32 +02:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-24 10:33:02 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2024-12-26 17:23:12 +02:00
2023-12-06 15:15:25 +02:00
2025-02-22 16:19:00 +01:00
2023-12-06 15:15:24 +02:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2024-11-19 12:27:22 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2025-02-22 16:19:00 +01:00
2024-11-19 12:27:22 +01:00
2025-02-22 16:19:00 +01:00