Multithreading EOAccess

Hi! 

Now that concurrent EOF operations are again possible by having multiple EOObjectStoreCoordinators there are some ‘smart tricks’ we are using that have me worried. 

The idea behind having multiple EOObjectStoreCoordinators is to get several independent EOF stacks. True, the EOControl level is duplicated. True, there will be several database contexts and channels. But what about the piece that sits right in-between: the model. 

It seems to me that there still is only one model group, one global copy of each model and entity. What I am worried about are tricks that modify an EOModel on the fly. E.g. one common one being to add a "count(*)" attribute to an entity in order to get a row count. I am afraid that such modifications might adversely affect concurrent fetches – either in performance or result. 

Is there a way to have multiple EOModelGroups – one for each EOF stack? 
Is there any global lock left that one could acquire in situations where one needs to block concurrent EOF operations? 

Pierre. 

 
---
Spinning WebObjects or cooking up Cocoa in Switzlerland?
Let me know: http://homepage.mac.com/I_love_my/