[Kolab-devel] Horde preferences: LDAP or IMAP?
Alain Spineux
aspineux at gmail.com
Mon Oct 8 17:03:06 CEST 2007
On 10/8/07, Thomas Arendsen Hein <thomas at intevation.de> wrote:
> * Martin Konold <martin.konold at erfrakon.de> [20071005 18:34]:
> > Am Freitag 05 Oktober 2007 schrieb Alain Spineux:
> > > Of course, "last write wins", but in a multi-user environement, you cannot
> > > make the update without care.
> >
> > With SQLite it is typical to use one db file per user. So there are no locking
> > issues.
>
> ... users never have two browser windows?
> ... people never press reload when they get impatient about the
> stalled browser connection?
> ... one account is never used by two people?
This was what I was worrying about !
BUT :
- most browser windows share the same cookie set and then the same session.
- having a _working_ horde should be fine, even with a
"single-connection/user" limitation.
- horde is not kolab server, horde is only a client, hode limitation
will not limit kolab server.
- This can be improved later without any chnage for the user.
- a php solution should exist for this case, if not please use a sql
library using a modular SQL driver, easy to change to a more SQL
scalable solution (mysql/posgress)
- if you wan horde working a multiple server you shoud use a salable
SQL solution.
Hope this help
Regards
>
> Thomas
>
> --
> thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
> Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
> Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>
--
Alain Spineux
aspineux gmail com
May the sources be with you
More information about the devel
mailing list