Details
-
New Feature
-
Resolution: Unresolved
-
Major
-
None
-
11.10.2
-
None
-
Unknown
-
Description
I propose that we create a very simple framework to allow using browser storage in our javascript calls.
The idea is the following: I want to access from Javascript to some options of the wiki to enable or disable features (e.g. to know if it's configured to use parentchild or reference hierarchy mode for example), now I don't necessarily want to make each time a REST call to retrieve this value since it can be costly very quickly.
So my idea would be to load some defined values in the session storage of the browser, and to reuse these values when needed. The storage would be reset when the values are edited.
We might discuss the benefits of this approach compared to put more stuff in xwiki-metadata: IMO this approach is more extensible (we won't rely on fixed keywords for the values, but on javascript objects) and fit its specific need: to make available on Javascript some values that are often read and rarely written.
AFAICS browser storage is compliant with our browser support strategy: I compared the data from https://www.w3schools.com/html/html5_webstorage.asp and https://dev.xwiki.org/xwiki/bin/view/Community/SupportStrategy/BrowserSupportStrategy
Attachments
Issue Links
- depends on
-
XWIKI-16946 Allow to access to XWikiPreferences properties in REST with guest
- Open
- relates to
-
XWIKI-16809 Cannot open the parent field after setting the hierarchy mode in preferences
- Open
-
XWIKI-16861 Define name cleanup strategies and prevent creation of pages with "/" and "\" in the name by default
- Closed