Metadata
- Source
- FLUID-5033
- Type
- Improvement
- Priority
- Major
- Status
- Closed
- Resolution
- Fixed
- Assignee
- Justin Obara
- Reporter
- Antranig Basman
- Created
2013-06-03T23:14:34.984-0400 - Updated
2014-03-03T11:49:14.457-0500 - Versions
-
- 1.4
- Fixed Versions
-
- 1.5
- Component
-
- IoC System
Description
In conjunction with FLUID-5032, it would be useful to be able to dynamically reload component defaults, especially for in-development scenarios or "live coding" situations. Right now for efficiency reasons, we have been cashing component default options on registration - this has been in place since late 2011 as part of a performance review in CollectionSpace - this caching was described in FLUID-4563. Getting the benefits of both dynamism as well as caching creates a more complex tradeoff, but it should be possible to implement a solution which allows re-issuance of component defaults without punishing regular users of cached defaults too much.
An ultimately iterated implementation of this functionality would allow for dynamic reloading of particular component instances which could be determined to be affected by changed defaults. This is a more ambitious work package outside the scope of this JIRA.
Comments
-
Antranig Basman commented
2013-06-30T01:40:10.563-0400 Merged into trunk at revision ba09d84