Most binaries only have 1 section to hold the additional information.

Please note that the objects themselves are not data-bound. They are simply information holders for corresponding data records. It's perfectly legal to construct a new object without data relevance, populate it with values, and use it to create a new record in the database.

It is also legal for one record to have several instances of representive objects. Therefore it is never a correct approach to compare object to object: two instances of same class are equal to each other if they have the same ID.

Interface for authenticator plugins to inherit. The plugin registration engine (IAuthenticationEngine) will detect and register the instance of any types inheriting this interface.

The authentication plugins are not in charge of providing actual user information, they are stored in the Cartella database. The plugin only need to find out if the user can authenticate with the respective system.

Default database authentication is carried out by LicenseManagerBase, not from this system.

The AdditionalProperties property is on the returning object module, is mainly used by BeforeConversion_TaskConfigurationChanges callback to adding arbitrary metadata.

The interface provides the basic functions for a Data-Bound object, including retrieving fields, getting the object ID, get/set of the object Name, get/set the field value by field name.

This interface defines the structure of objects that allows batch update.

Objects in Cartella general have real time database update, as properties being set. This makes Cartella API intuitive and easy to use. However, there are times when we don't want every property set to cause a database transaction. Here is where IBatchUpdatable coming. It allows batch of property updates to be grouped together and perform database transaction only once afterwards.

This is done by set "StopEventUpdate" property to true and stop all property changes from triggering events issued FieldCollections, which is the driving force of per-property updates.

Represents the Singleton object, which is the hub os all Cartella objects, managers and events.

Its main purpose is to maintain a list of SiteManager instances, also relay all events issue from the SiteManager instances.

CartellaGlobalManager is designed to hold a given number of SiteManager instances and keep them around. There will be a expiration time set on each SiteManager. If within the expiration time threshold, no Methods or Properties calls happened on the SiteManager instance at all, the SiteManager instance will be automatically dropped from the pool and erased.

This system allows system not need to create a SiteManager instance everytime, also in the same time, not use too much memory to store every unsed SiteManager instances.

Defines the manager interface for specific object type that is derived from ICartellaObject. All object type managers (e.g. CategoryManager, UserManager) derive from it

Classes inplementing this interface will have access to DataAccess Layer, knows data access manager, can get hold of the default procedures module to locate the ObjectDateProceduresImplementaion during construction.

It is in charge of casting a string, IField, or generic object value to the desired Database Parameter type.

Represents the Session-Independent part of License management system.

LicenseManagerBase is designed to be a singleton object. It holds the license information for the entire Cartella instance. It is also in charge of authentication/unauthentication of users.

Please note that LicenseManagerBase is only in charge of holding the licensing information. Assignments of user/seats is done by its user specific counter part - LicenseManager. It takes a actual user to do the actual licensing works.

Each request session will create a new SiteManager object.