You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Otto Fowler (JIRA)" <ji...@apache.org> on 2017/06/13 04:16:02 UTC
[jira] [Updated] (METRON-994) STELLAR Shell and management should
front the METRON REST api
[ https://issues.apache.org/jira/browse/METRON-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Otto Fowler updated METRON-994:
-------------------------------
Description:
As the rest api evolves to serve the management functionality of the UI, we are in danger have having functionality split or duplicated between the REPL and the REST interface.
Since the REST interface is going to drive the UI and be the official interface, STELLAR REPL should be refactored as a front to rest.
This will have the benefit of eliminating duplication of code and functionality, and drive new functionality to the REST api.
What we may end up having are classes of stellar statements: core language statements, locally executed in the REPL and 'service' type statements sent to rest.
We should map out the functions and an order of solve for moving them.
was:
As the rest api evolves to serve the management functionality of the UI, we are in danger have having functionality split or duplicated between the REPL and the REST interface.
Since the REST interface is going to drive the UI and be the official interface, STELLAR REPL should be refactored as a front to rest.
This will have the benefit of eliminating duplication of code and functionality, and drive new functionality to the REST api.
It will also make the REPL portable. We should strive to make the repl as small as possible, able to be run from any java capable workstation.
We should map out the functions and an order of solve for moving them.
> STELLAR Shell and management should front the METRON REST api
> -------------------------------------------------------------
>
> Key: METRON-994
> URL: https://issues.apache.org/jira/browse/METRON-994
> Project: Metron
> Issue Type: Improvement
> Reporter: Otto Fowler
> Assignee: Otto Fowler
>
> As the rest api evolves to serve the management functionality of the UI, we are in danger have having functionality split or duplicated between the REPL and the REST interface.
> Since the REST interface is going to drive the UI and be the official interface, STELLAR REPL should be refactored as a front to rest.
> This will have the benefit of eliminating duplication of code and functionality, and drive new functionality to the REST api.
> What we may end up having are classes of stellar statements: core language statements, locally executed in the REPL and 'service' type statements sent to rest.
> We should map out the functions and an order of solve for moving them.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)