We're using PersistentDictionary in one of our applications, and depending on the configuration of our application n instances of the persistentDictionary will be created.
The result is pretty much what's already described in
, so we can't continue to use it as it is.
I read through above discussion, but I doubt it's possible to solve our requirement through artifical keys - many implementation details (like locking) would leak to business layers and the performance IMHO would decrease as well.
Walking through the code I think that it's possible to rewrite and configure some of the internals like CreateGlobalsTable/CreateDataTable so multiple PersistentDictonaries can reside in a single database. This way it should (could?) be possible that it can
be used as before and can keep up the performance.
Do you think that this can be achieved or do you think it's better to remove PersistentDictionary from our application and use the JET API directly?