<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">I can't see storing this kind of thing in standalone.xml or host.xml, so this means some other form of persistent store. The use cases around managing that store would have to be gone through carefully.</div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">The content repository can be used for that kind of thing, but it's not meant to be directly managed. So no supported copying of your content from one instance to another, etc, at least not without specific tooling we'd have to provide. </div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><div class="gmail_default"><br></div><div class="gmail_default">People would also expect to be able to migrate this content when upgrading. Which is just a variant of copying your content from one instance to another.</div><br class="gmail-Apple-interchange-newline"></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">For a domain the content repository is a domain-wide store (which is actually a pro, since it means any host that is in sync with the domain can become master and know it will have the needed data.)</div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">How would this relate to possible uses of HAL in cloud environments?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 4, 2019 at 6:05 AM Harald Pehl <<a href="mailto:hpehl@redhat.com">hpehl@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The management console uses various settings which need to survive a browser <br>
restart. Currently these settings are stored client side only either as cookie or <br>
in the browser local storage:<br>
<br>
# Cookie<br>
<br>
- Google Analytics on/off<br>
- Page size<br>
- Poll on/off<br>
- Poll time<br>
<br>
# Local Storage<br>
<br>
- Management endpoints (for HAL standalone mode)<br>
- Pinned items in the finder<br>
- JavaScript extensions<br>
- Macros<br>
<br>
Using the browser to store settings has the advantage of being very flexible. <br>
The settings are also not bound to a specific WildFly instance. For some <br>
settings like the management endpoints this is a requirement and won't change. <br>
<br>
However other settings make more sense if they are stored on the server side. <br>
That's why I'd like to propose a dedicated subsystem for HAL. It should hold <br>
the current settings (except the management endpoints). It should be extendable<br>
to store additional settings (currently there's an RFE to customize the <br>
visibility of notifications in HAL). <br>
<br>
Another advantage is that settings and data like macros could be properly <br>
secured using RBAC. <br></blockquote><div><br></div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif">How so?</div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif"><br></div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif">I assume content would be per user so access to parts of the content would be restricted based on userid.</div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif"><br></div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif">Perhaps some kind of administrative operations that give access to other users content, use of which would be limited based on the WildFly RBAC roles?</div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif"></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I would like to hear your opinion about a dedicated subsystem for HAL. <br>
Does it makes sense? How should it look like? Any feedback and comments are <br>
welcome!<br>
<br>
// Harald<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Brian Stansberry<div>Manager, Senior Principal Software Engineer</div><div>Red Hat</div></div></div></div>