[
https://issues.apache.org/jira/browse/AIRAVATA-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892246#comment-13892246
]
Chathuri Wimalasena commented on AIRAVATA-1006:
-----------------------------------------------
Hi Marlon, Suresh,
Please give feedback to [1]. Will this be too abstract ? Someone who programs
against this should only know about the thrift data models. He does not have to
know about the registry structure.
[1]
https://git-wip-us.apache.org/repos/asf?p=airavata.git;a=blob;f=modules/registry/registry-cpi/src/main/java/org/apache/airavata/registry/cpi/Registry.java;hb=25cc2514
> Craft the Registry 1.0 CPI
> --------------------------
>
> Key: AIRAVATA-1006
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1006
> Project: Airavata
> Issue Type: Sub-task
> Reporter: Suresh Marru
> Fix For: 0.12
>
>
> As the Airavata API is evolving towards 1.0 version, we need to refine the
> currently Registry API (and the current Airavata Client->Registry API) into a
> unified and well defined Registry CPI.
> This registry CPI is targeted to be invoked by the Airavata API functions and
> use of Registry by all internal Airavata internal components like
> Orchestrator, Workflow Interpreter and GFac.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
