Dear Wiki user, You have subscribed to a wiki page or wiki category on "Directmemory Wiki" for change notification.
The "ProposedRoadmap" page has been changed by RaffaeleGuidi: http://wiki.apache.org/directmemory/ProposedRoadmap?action=diff&rev1=4&rev2=5 DirectMemory has been recently entirely rewritten for simplification. It used to have three layers (heap, off-heap, file/nosql) and to authomatically push forward/backward in the chain items according to their usage. It turned out overly complicated and mostly inefficent at runtime (probably mostly because of my poor implementation). The singleton facade is proving simple and effective and well refects the nature of direct memory - which cannot be really freed. But this needs a strategy for feature and behaviour composability. Singleton (largely Play! inspired) approach - is it good? - Feature and behaviour composability (DI and Feature injection? A plugin system? OSGi?) - just let's keep things simple and developer friendly. Proposals: + Feature and behaviour composability (DI and Feature injection? A plugin system? OSGi?) - just let's keep things simple and developer friendly. Proposals is to keep existing facade but adding: - * '''Fluent API''' + * A '''Fluent API''' * '''Separate Modules for DI systems''' - Guice first and Spring if needed == New features ==
