[
https://issues.apache.org/jira/browse/METRON-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044973#comment-16044973
]
Nick Allen commented on METRON-994:
-----------------------------------
I agree with you that we would want to avoid duplication here.
For example, are you thinking of something like CONFIG_GET, right? Both the
REPL and REST API need to be able to do something like that.
What are the cons of the mirror approach of what you are suggesting? The
single, concrete implementation is the CONFIG_GET Stellar function. The REST
API would simply execute this function server-side in the same way that the
REPL executes this function.
> 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.
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
