[ 
https://issues.apache.org/jira/browse/HBASE-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399709#comment-13399709
 ] 

Todd Lipcon commented on HBASE-6259:
------------------------------------

bq. If a minimal ui is all that we invision ever having then just keeping jamon 
and moving the last pages off of jsp seems the best. However if we want to have 
things like monitoring and trending (stack you and I had mentioned this), a 
shell (someone at hadoop summit mentioned this), and configuration (we started 
talking about dynamic configs lately) all on the ui then I think it could be 
worth it to go to a more modern and adopted framewor

IMO we should keep the built-in pages simple, and expose all the right APIs so 
that an external "fancy" UI can be built. The fancier we make the built-in UI, 
the more likely we have bugs in it, and the less likely it'll be usable from 
command line browsers like lynx (yes, I do that reasonable often!). It also 
tends to result in cases where we have data that's only visible through the UI, 
which encourages people to start scraping HTML to gather metrics, etc.

On the other hand, if everything's available via APIs, then we can have an 
external web UI with all the whiz-bang features we want. The external UI might 
be another daemon running in the HBase project. I think Accumulo takes 
basically this approach (theirs is called the "Monitor" process, and it talks 
to the actual daemons via thrift, as far as I understand)
                
> Unify all of the templates into one templating language
> -------------------------------------------------------
>
>                 Key: HBASE-6259
>                 URL: https://issues.apache.org/jira/browse/HBASE-6259
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>    Affects Versions: 0.96.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>              Labels: noob
>
> Right now .jsp and jammon templates can't share common parts as they are 
> un-related.  We should move to one templating language.  Maybe also move away 
> from jamon.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to