[Kroupware] OpenGroupware.org formed through SKYRiX open sourcing its Groupware server

[Martin Konold]

Am Sonntag, 13. Juli 2003 02:26 schrieb Helge Hess:

Hi,

> exactly that is supposed to be a problem. Kolab avoids locking
> conflicts by killing the "update" operation in the store and replacing
> it with "create new, delete old". This removes a whole lot of locking
> issues, but loses object identity (eg, duplicate records can be created
> which need to be merged in the application layer).

Yes, this is correct. Basically the processing power of all clients increases 
while the number of clients increases so putting this effort on the client 
helps scalability a lot.

On the other hand the processing of "duplicates" on the client is a rather 
seldom operation.

General rule: Make the server as fast as possible as it is the bottleneck and 
optimize for the common case not the exception.

Regards,
-- martin

Dipl.-Phys. Martin Konold

e r f r a k o n
Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
Nobelstrasse 15, 70569 Stuttgart, Germany
fon: 0711 67400963, fax: 0711 67400959
email: martin.konold at erfrakon.de