[Kroupware] Questions about Shared Resources & Concurrent Access
Martin Konold
martin.konold at erfrakon.de
Mon May 19 23:45:16 CEST 2003
Am Montag, 19. Mai 2003 18:25 schrieb Diego Rivera:
Hi,
> Well...here's the thing: room1 might not necessarily have a person
> assigned to confirm bookings to it.
>
> Assume two users: user A and user B trying to get a 1 hour, 1:00pm
> meeting with resource X.
>
> A and B both try to get the appointment at the same time, read the
> existing appointments, realize 1:00pm is open, and book the
> appointments. Thus, 1:00pm is double-booked. In the scenario I
> describe, the correct behavior would be that one of them gets bounced
> because the other beats them in the race.
>
> However, this gets complicated to do (using anything short of a
> dedicated calendaring server product) using file-transfer mechanisms.
> Mutex locking with file transfers run the risk of clients holding locks
> through crashes, which is NOT correct behavior.
Well, basically the user trying to book a ressource has to wait for the
confirmation. The kde kolab client only sends a single confirmation on a
first come first serve race in case you chose the automatic mode.
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
More information about the Kroupware
mailing list