This utility provides the capability for creating pipelines that pass messages between Cores in a PureMVC  MultiCore-based application. Pipelines can be composed of filters, queues, splitting and merging tees, and more.

The Utility is located here: https://github.com/PureMVC/puremvc-swift-util-pipes/wiki

Authors are Cliff Hall and Saad Shams.

The Project Owner is Saad Shams. <saad.shams@puremvc.org>

This utility provides a simple yet effective Finite State Machine implementation, which allows the definition of discrete states, and the valid transitions to other states available from any given state, and the actions which trigger the transitions.

A mechanism is provided for defining the entire state machine in XML and having a fully populated StateMachine injected into the PureMVC app.

The utility is is located on GitHub: https://github.com/PureMVC/puremvc-swift-util-statemachine/wiki

The authors are Neil Manuell, Cliff Hall, and Saad Shams.

The Project Owner is Saad Shams. <saad.shams@puremvc.org>

The project source is hosted at GitHub:
https://github.com/PureMVC/puremvc-swift-multicore-framework/wiki

The Project Owner is:
Saad Shams <saad.shams@puremvc.org>

Based on a need to handle a series of asynchronous operations. Ultimate use in conjunction with AsyncCommands/AsyncMacroCommands in a sequence.

The AsyncProxy Utility source is on GitHub:
https://github.com/PureMVC/puremvc-swift-util-asyncproxy/wiki

The author is Saad Shams. <saad.shams@puremvc.org>

The AsyncCommand utility offers a solution to the problem of executing a series of commands each of which may need to complete one or more asynchronous operations before the next command is executed.

The source code is located on GitHub: https://github.com/PureMVC/puremvc-swift-util-asynccommand/wiki

Standard and MultiCore versions are included.

The author is Saad Shams. <saad.shams@puremvc.org>

The AsyncCommand utility offers a solution to the problem of executing a series of commands each of which may need to complete one or more asynchronous operations before the next command is executed.

The source code is located on GitHub: https://github.com/PureMVC/puremvc-swift-util-asynccommand/wiki

Standard and MultiCore versions are included.

The author is Saad Shams. <saad.shams@puremvc.org>

Based on a need to handle a series of asynchronous operations. Ultimate use in conjunction with AsyncCommands/AsyncMacroCommands in a sequence.

The AsyncProxy Utility source is on GitHub:
https://github.com/PureMVC/puremvc-swift-util-asyncproxy/wiki

The author is Saad Shams. <saad.shams@puremvc.org>

This demo illustrates techniques for performing routine maintenance operations in a PureMVC-based Swift / UIKit application.

The project source is hosted on GitHub: https://github.com/PureMVC/puremvc-swift-demo-uikit-employeeadmin/wiki

The author is Saad Shams. <saad.shams@puremvc.org>

The project source is hosted at GitHub:

https://github.com/PureMVC/puremvc-swift-standard-framework/wiki

The Project Owner is:
Saad Shams <saad.shams@puremvc.org>

Essentially your system of Proxies do the same thing as the DAOs. The DatabaseProxy would have the reference to the DB and the CRUD logic. The BooksProxy, et al, would manage a set of BookVOs and expose methods for getting them or setting them so the rest of the app interacts with them and not the DatabaseProxy. Those classes wouldn't extend the DatabaseProxy (which has as its data object the database itself), but would interact with it via composition. During startup of the app, while preparing the model, you would create the DatabaseProxy first, and then create all the other proxies like BookProxy and give them references to the DatabaseProxy. They'd hang onto that proxy and make calls on it.

If you wanted to support multiple databases, then make an IDatabaseProxy interface, and have all the proxies like BookProxy interact with DatabaseProxy using the interface. So instead of DatabaseProxy, maybe its SqlLightDatabaseProxy. Then if another DB comes along, you build another proxy that implements IDatabaseProxy and provide that to your per-table proxies.