Handle FID/MID uniqueness BY MAILBOX rather than BY SERVER
authorJulien Kerihuel <j.kerihuel@openchange.org>
Tue, 25 Jan 2011 22:30:36 +0000 (22:30 +0000)
committerJulien Kerihuel <j.kerihuel@openchange.org>
Tue, 25 Jan 2011 22:30:36 +0000 (22:30 +0000)
commitd8e6802441fd93654ab946989c36912bea440183
tree5b963e5fdd886fbd1dc77ba8f6a9ea11fa593696
parent3ec23632c42d927ea297c7bfebe4b081b47df14f
Handle FID/MID uniqueness BY MAILBOX rather than BY SERVER

The FID/MID namespace is unique per mailbox which means that even if
you get out of IDs, you only crash your mailbox, not the entire
server

The following commit introduces a user store object within mapistore.ldb located
under CN=${username},${firstorgdn} responsible from maintaining the GLobalCount
for the user mailbox.

Furthermore, this alters the core behavior of provisioning and introduce username
as being a parameter to most of the mapistore API (propagation scheduled among
mapistore_v1 to mapistore_v2 transition).
mapiproxy/libmapistore/backends/mapistore_mstoredb.c
mapiproxy/libmapistore/database/mapistoredb.c
mapiproxy/libmapistore/mapistore.h
mapiproxy/libmapistore/mapistore_backend_public.c
mapiproxy/libmapistore/mapistore_interface.c
mapiproxy/libmapistore/mapistore_private.h
mapiproxy/libmapistore/mapistore_processing.c
pyopenchange/pymapistoredb.c
pyopenchange/tests/mapistoredb_test.py