| Cache and global context [message #1761285] |
Tue, 09 May 2017 09:34 |
Eclipse User |
|
|
|
Currently, global context is usable only with very simple String objects. If you tried to save an object from a scripting service and retrieve it you will run into trouble most likely.
Now, I'm aware that we all hate states, but truth be told, caches (context being sort of an app cache) enable a number of use cases and even twelve factor apps paradigm does not deny that. They just refer to it as in-memory backend service.
We should therefore explicitly outline the place for cache and the kind of objects (and data size) that we aim at supporting.
Does it require and enterprise API any different than the global set/get we have now? Or we should be able to fine tune the eviction policies?
|
|
|
Powered by
FUDForum. Page generated in 0.08125 seconds
Home