After taking a look at the default core Enterprise Objects stack, you’re probably wondering why there are so many different kinds of object stores. These objects are all subclasses of EOObjectStore: EOObjectStoreCoordinator, EOCooperatingObjectStore, EODatabaseContext, EOEditingContext. The short answer as to why there are so many kinds of object stores is that the different object stores know different things about enterprise object instances.
An editing context, for example, has no direct knowledge of how to initiate a transaction with a database. A database context, however, does. An editing context, also, has no knowledge that the enterprise objects it holds may be constituted with data from multiple distinct data repositories. An editing context’s object store coordinator, however, knows this and knows how service requests that require managing data from disparate sources.
While you don’t need to understand the complexities of all these types of object stores or how they interact, just know that they each play an important role within the frameworks.
Last updated: 2007-07-11