Application Harness#
Situation (UI)#
There are a number of APPXC objects involved to cover cross functional concerns leading to repeated code patterns:
the objects must be initialized in a ceratin order due to their dependencies
login and registration are common procedures
To be refined:
(??) common procedures may not be good argument - why are those not included in the security or registry object??
login procedure includes user configuration - a dependency not wanted for security object
registration procedure may be different dependent on how registration requests and responses can be exchanged
most important: procedure implies needing UI
included: security, configuration, registry and/or storage locations.