Developer's Guide - EPiServer World

16 | Developer’s Guide EPiServer Community 3.1
1.3 Namespaces
1.3.1 StarSuite.Core
The StarSuite.Core namespace contains important startup classes like Settings, Site and SiteHandler and takes care of
loading modules in the correct order based on dependencies.
1.3.2 StarSuite.Core.Cache
The StarSuite.Core.Cache namespace contains the EPiServer Community Cache system. The cache is based on a treestructure
with the ability to have dependencies between branches. Every cached object in products like EPiServer
Community implements the ICacheable interface, allowing an object to have a primary cache key. The cache then keeps
track of changes to this cache key and released other caches that also contain this object. All these features in
conjunction make the EPiServer Community cache a lot more precise than in previous versions.
The new cache system also implements the policy of read-only objects in cache. This is a big change since previous
versions, since now objects retrieved from methods needs to be cloned before any properties are updated. All
EPiServer Community entities have a Clone() method that will return a writable copy of the object.
1.3.3 StarSuite.Core.Data
The StarSuite.Core.Data namespace contains the database communication layer. It is called by all Factory classes to
open connections and transactions and makes it possible to run several method calls within one transaction.
bool alreadyInTransaction = DatabaseHandler.InTransaction;
if(!alreadyInTransaction)
DatabaseHandler.BeginTransaction();
try
{
// execute a series of methods,
// they will all be in the same transaction
AddUser();
SetAccessRights();
// we are only responsible for commiting the transaction
// if we were the ones to start it
if(!alreadyInTransaction)
DatabaseHandler.Commit();
} catch
{
if(!alreadyInTransaction)
DatabaseHandler.Rollback();
throw;
}
© EPiServer AB