Multiple Coordinators, shared editingcontext and more

I need to have editing context that aren't notified between then of changes(want to use optimistic locking all the time, dont want update trouble between objects, we would like to have something like e UnitOfWork), i need to have multiple connections to the database(we have a lot of very large transactions), I need all my editing context to share some common entities that dont change very often(in order to have less cache data). 

What we thought here is to have some kind of wrapper that has an internal ObjectStoreCoordinator, an internal editing Context, and a sharedEditingContext common to all the instances of this wrapper.

So, each session must get a wrapper instance and work with it. The user should never know if its using an object from the sharedEC or the commonEC. The wrapper should handle moving an object from the sec to the ec when the user wants to edit or delete an object.

What we dont know if this is a proper approach to the problem, and if it is, if thw wrapper should extend or not EOEditingContext.

Thanks!
__________________________________________________

Todavía no tenés tu Ciudad Internet Mail? Obtenelo ahora! - http://webmail.ciudad.com.ar

Descargá Gratis el nuevo Internet Explorer 6.0, el mejor software para actualizar tu PC.
http://www.ciudad.com.ar/ar/servicios/ie/