On Thu, Jul 06, 2006 at 02:02:43PM +0300, Peter Damoc wrote:
>> When a patient is edited on the laptop that patient is
>> marked as changed.
>
> This is so simple... :) why didn't I think of it before.
> I just keep a log of "changed" patients on both machines and simply replace
> the old patients if there is no conflict
Yep, if you can guarantee non-concurrency this is a nicely
workable approach.
I can enforce a solution that will forbid concurrency. Concurrency is of little importance compared to Consistency.
I might be mistaken but this is one of the problems I perceived at GNUMed... overdesign.
> or use a simple conflict solver for the patients that changed on both machines.
Well, and that's the problem. The conflict solving may not
be a simple issue. But surely worth trying.