On 21.02.23 23:42, Julien Grall wrote:
Hi Juergen,
On 21/02/2023 08:37, Juergen Gross wrote:
On 20.02.23 23:50, Julien Grall wrote:
+ list_del(>list);
+ talloc_free(cd);
+ }
+}
+
+void acc_commit(struct connection *conn)
+{
+ struct changed_domain *cd;
+ struct
Hi Juergen,
On 21/02/2023 08:37, Juergen Gross wrote:
On 20.02.23 23:50, Julien Grall wrote:
+ list_del(>list);
+ talloc_free(cd);
+ }
+}
+
+void acc_commit(struct connection *conn)
+{
+ struct changed_domain *cd;
+ struct buffered_data *in = conn->in;
+ enum accitem
On 20.02.23 23:50, Julien Grall wrote:
Hi Juergen,
On 20/01/2023 10:00, Juergen Gross wrote:
Instead of modifying accounting data and undo those modifications in
case of an error during further processing, add a framework for
collecting the needed changes and commit them only when the whole
Hi Juergen,
On 20/01/2023 10:00, Juergen Gross wrote:
Instead of modifying accounting data and undo those modifications in
case of an error during further processing, add a framework for
collecting the needed changes and commit them only when the whole
operation has succeeded.
This scheme can
Instead of modifying accounting data and undo those modifications in
case of an error during further processing, add a framework for
collecting the needed changes and commit them only when the whole
operation has succeeded.
This scheme can reuse large parts of the per transaction accounting.
The
