Hi, I've been working on getting the server back running for mapistore_v2 branch, and one idea that seems quite useful is to treat all the folder information we need to add as just a set of named properties.
So if we need a mailbox GUID and mailbox replica GUID, we could just store those as properties on the mailbox root folder. The backend operation would just be the standard op_getprops. I'm currently working on an implementation that does this for mailbox properties. However I recognise that the properties are a scarce resource (only 16 bit space, 15 bits for the direct ids and 15 bits for the named properties). However we don't need to use the same space as the wire protocol for this. That led to thinking about the best way to handle properties (both direct ID and named properties). It occurs to me that we could perhaps handle all properties using a larger space (perhaps 48 bits for property "number" + 16 bits for property type) which would include a GUID index (for the property namespace) together with either the property number or a name index. So on receipt of the property tag from the client, we'd map that into a server representation. That could make lookup of LID pretty easy, and might be able to be shared across the whole server. Each user would still have a mapping for their 16 bit property ids. Thoughts about the treatment of folder characteristics as generic properties? Thoughts about the best way to manage the properties space? Brad _______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
