[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] concurrency error detection in business objects

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] concurrency error detection in business objects
Date: Mon, 8 Nov 2004 22:08:25 +0100
User-agent: Mutt/

> I can't see any problems with this approach, I note it has been nicely
> abstracted in the business layer, can we do this in the GUI calling code too?
I wish we could but I don't think we can.

> My fear is that every time we call a business object to commit data, 
> we end up doing this:
Likely, yes.

My worry is that user interaction is just too varied
(especially what type of reaction is wanted should one
encounter a concurrency conflict) to be abstracted away. In
some cases I may know that my version of the data is
definitive, no matter what happened elsewhere. In that case
I'll just redo the transaction if it fails. In other cases I
will have to alert the user and/or let her re-edit the changed

I do think, however, that we'll be able to teach some of the
widgets to generically handle such errors. I am thinking of
the edit area first. I'll likely write a child class of
cEditArea which knows how to handle cBusinessObject children.

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]