Description Jeff McAffer 2006-10-14 07:15:31 EDT

Currently the state is written out as one big chunk per configuraion.  There are a couple use cases for changing this and allowing the state to be fragmented.

1) early startup processing.  Doing the splash screen and allowing for user/role-based configurtions would both benefit from the ability to load a small state, do some processing and then extending the state either from more parts of the same cache or from an additional cache

2) bug 134498 describes a use case for having instance area specific bundles (thus implying state).

Would be interesting to look at what it would take to enable these usecases