<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">TL;DR<div class=""><br class=""></div><div class="">For management clients it is tedious and awkward to read resources / attributes in big domains (e.g. return the state of all running servers across all hosts which are part of server group "foo"). Today this requires to setup multiple composite operations *on the client* which need to be executed in a specific order. This proposal suggests a new operation which collects all relevant information *on the server* and returns only the relevant data in one go to the client.</div><div class=""><br class=""></div><div class="">--------------------</div><div class=""><br class=""></div><div class=""># Background:</div><div class=""><br class=""></div><div class="">In the admin console we often need to read specific attributes across a domain or across a deeply nested resource: </div><div class=""><br class=""></div><div class="">- List all enabled data sources of the current profile </div><div class="">- Show the port offset of all running servers across all hosts</div><div class="">- Get all users which belong to role Operator</div><div class=""><br class=""></div><div class="">Even for small domains with two server groups and a small number of servers this procedure is awkward and error prone. What makes it even more difficult is the asynchronous nature of the admin console. Soon you end up in a deeply nested callback-hell. Besides that these 'queries' lead to poor performance for big domains with tens of groups, hosts and servers. </div><div class=""><br class=""></div><div class=""># Proposal / Prototype</div><div class=""><br class=""></div><div class="">The GitHub repository at [1] contains a more detailed description of the problem statement and a working prototype. This includes details such as how to address the requested resources, how the information is retrieved and how to handle errors. </div><div class=""><br class=""></div><div class="">The proposal also includes a way to filter and reduce the resources against a list of attributes and values *before* the response is sent to the client. </div><div class=""><br class=""></div><div class="">[1] <a href="https://github.com/hpehl/map-reduce" class="">https://github.com/hpehl/map-reduce</a> </div><div class=""><br class=""></div><div class="">---</div><div class=""><div apple-content-edited="true" class="">Harald Pehl<br class="">JBoss by Red Hat<br class=""><a href="http://hpehl.info" class="">http://hpehl.info</a><br class="">
</div>
<br class=""></div></body></html>