Feature #2255
replace non-UI code that has direct dependencies on the UI with dependence on an abstract provider that can be registered at runtime
0%
History
#1 Updated by Greg Shah over 10 years ago
Provide an abstract interface for UI services used by code in p2j/util/ et al. For example, the TransactionManager, BlockManager, ErrorManager and other places in the code may have some ui or ui/chui dependencies. Rather than hard coding these dependencies, it would be much better to have a simple service API for the core features needed. Then the provider of that API can be registered in each session as needed. This will make for cleaner separation but it will also help pave the way for server-side UI processing, which is needed for batch mode, appserver support and webspeed.
An start on this was made recently with some improvements to the ErrorManager. However, the full set of dependencies need to be reviewed and abstracted to finish this work.