[
https://issues.apache.org/jira/browse/METRON-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044992#comment-16044992
]
Otto Fowler commented on METRON-994:
------------------------------------
Yes, this occurred to me while working on METRON-947 doing just that.
I am going to admit, I did not even think about putting rest in front of
stellar, and when I talked with [~cestella] earlier I don't think that occurred
to him either. For some reason, I was thinking the REST api was going to be
the api of record, but nobody has really made that decision have they. I would
like to think about that some. That is a really good option. And if we get
some clarity as to the api etc that would be good too.
> 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)
