High level architecture, AW2

Not everything need be in one program, if we've got a good dividing point, and I think I've got one.

On the back end:

• wdb,
• tables,
• resolution engine,
• dump/snap/restore,
• command interpreter and
• single writer, many reader flow control.

Front ends (more than one):

• email
• genjnl
• user interface(s)

Make the back end Java. Define the interface well. And the front end can be any language or web server you find most appropriate.

Each interaction between the back end and a front end would be a transaction or a query.

Bill