Next Generation Architecture
Discussion for design and implementation of a next generation overhaul to MoinMoin's architecture. This includes elements such as the Summer of Code 2006 storage refactoring project.
- [get | view] (2006-09-03 22:59:18, 100.2 KB) [[attachment:MoinArchDiagram.png]]
- [get | view] (2006-08-30 21:00:37, 52.7 KB) [[attachment:Phase1Arch.png]]
- [get | view] (2006-08-30 21:29:26, 73.7 KB) [[attachment:Phase2Arch.png]]
- Engines shared by multiple namespaces have potential problems when a namespace adds a page. A namespace must only add the page to this engine if the item does not exist in the entire namespace of all namespaces that use this particular engine. Or another approach is allow an item to be a member of multiple namespaces?
- Namespaces can be built with specific rules over which engines data is saved upon by its implementations discretion.
Namespace parameter to item creation could dictate which namespace is to be used. Namespace must verify by its rules if a certain ItemRevisionType is allowed within it.
- Potentially all transactions are processed with a session object rather than passed every time to the SI by value. This will reduce memory and speed as it will cache generated paths related to the engine temporarily.