design decisions for AW2

1. single writer, multiple readers

This keeps the transaction logic really simple. No locking. No file locks. And as the front ends are unaware, it can be changed later.

2. each interaction with the back end is a transaction

The advantage here is that transactions are confined to the back end--mucho reliability and stability.

The cost is that application logic must be installed on the back end.

Correction:

As genjnl wants to be a single transaction, the logic must be on the back end. But we'll have an operator front end for requesting genjnl, dump, snap, restore, dumpcabinet, snapcabinet and installcabinet.

Another front end: RSS reader?

Also for consideration: notifier for changes, published either as RSS feeds or email.

(Hey, I can dream, can't I?)

And you know, this all does NOT sound like a one man project. I sure could use some help.

Bill