Repository Performance Considerations
- Repository code has taken ease of implementation over performance.  There are many performance problems as outlined here
- No object caching
- No object recycling
- push caching up thru the objecthandler/classhandler hierarchy, if possible.  Perhaps removing object handler would be nice.  Rethink auto class handler registration thru configuration... perhaps some sort of registration with static manager on create, like jdbc driver class, tho auto handler loading on access would be nice. ca.reachable.repository.basic.handlers.XHandler where X is name of class to be persisted.  Or combo of both... ie try load if not registered.
- push class handler functionality into generic xml-based handler.  Move info into xml file.  Maint info and schema at same time with high level tools.  Cache cache cache.  Including query definitions.  Reload on file change.
- investigate automation of ram drive database.  perhaps a flag to RepositoryApplications
- run big query thru profiler