Github user echarles commented on the issue:
https://github.com/apache/zeppelin/pull/2418
@jongyoul sorry, I was not clear enough. With frontend, I was meaning the
web layer (so jetty). Jetty could communicate via a variety of protocols to the
interpreters. Now going further in that direction, having protocols like REST
or WebSocket would allow any king of clients to access the interpeters in
direct - Those clients could be the current javascript of Zeppelin webapp, or
any other kind of client (could be bash or python script...)
This is unique opportunity to extend the Zeppelin user base - Btw, having
the AAA (Authentication, Authorization, Auditing) functions at Interpreter
level is IMHO a good design, even at the cost of some extra development or
refactoring.
I am curious to know what the community thinks about this...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
