The CowDb and COODBMS databases have been updated with new features and enhancements for improved performance and ease of use.
AgileWiki CowDb2 is a software rewrite that includes large chunks of code from CowDb and COODBMS, with only a few architectural changes for improved scalability. The purpose of this rewrite is to bring clarity to the object model, particularly the Elements which became muddled during the implementation of COODBMS. The COODBMS Browse client will remain unchanged.
The software begins with Rolons, which function similarly to JavaBeans and consist mostly of framework objects. Although they are moderately small, they are scalable enough to build large indexes. Rolons serve as the building blocks of applications and are comprehensive in their capabilities. Four subtrees comprise each Rolon: the classifier unit, the descriptor unit, the ledger unit and the journal unit. These subtrees are responsible for Rolon relations, behavior, state and history. Each Rolon maps directly to an XML document composed of Elements.
Elements are the building blocks of Rolons and also used in the framework. Elements aggregate simple objects implementing different aspects of the element. There are multiple implementations for each aspect, and the aspects include Attributes, Contents, Handle, Names, Rolonic, and Application. The Application aspect is where to add logic specific to the framework or Rolon's use. However, it's important to note that all persistent data is maintained by the attributes, contents, and handle objects, and application objects are not persistent. Thus, there is only a limited number of Persistence, Attributes, Contents, and Handle classes and are all part of the framework.
Every Element has a role that defines its capabilities and usage. The role name doubles as the name for the XML element. A Properties object associates each applicable aspect of an element with a class based on its role name. For instance, the property for dbRoot elements to use an instance of the CAttributes class for its attributes aspect would look like this: dbRoot.attributes = CAttributes.
The software begins with Rolons, which function similarly to JavaBeans and consist mostly of framework objects. Although they are moderately small, they are scalable enough to build large indexes. Rolons serve as the building blocks of applications and are comprehensive in their capabilities. Four subtrees comprise each Rolon: the classifier unit, the descriptor unit, the ledger unit and the journal unit. These subtrees are responsible for Rolon relations, behavior, state and history. Each Rolon maps directly to an XML document composed of Elements.
Elements are the building blocks of Rolons and also used in the framework. Elements aggregate simple objects implementing different aspects of the element. There are multiple implementations for each aspect, and the aspects include Attributes, Contents, Handle, Names, Rolonic, and Application. The Application aspect is where to add logic specific to the framework or Rolon's use. However, it's important to note that all persistent data is maintained by the attributes, contents, and handle objects, and application objects are not persistent. Thus, there is only a limited number of Persistence, Attributes, Contents, and Handle classes and are all part of the framework.
Every Element has a role that defines its capabilities and usage. The role name doubles as the name for the XML element. A Properties object associates each applicable aspect of an element with a class based on its role name. For instance, the property for dbRoot elements to use an instance of the CAttributes class for its attributes aspect would look like this: dbRoot.attributes = CAttributes.
What's New
Version 0.3: N/A