airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Marru (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AIRAVATA-1005) Rename and Enhance the Airavata Component Interfaces (CPI)
Date Thu, 31 Jul 2014 15:18:39 GMT

     [ https://issues.apache.org/jira/browse/AIRAVATA-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Suresh Marru resolved AIRAVATA-1005.
------------------------------------

    Resolution: Fixed
      Assignee: Suresh Marru

The CPI's are functional and bundled into 0.12 and subsequent releases. 

> Rename and Enhance the Airavata Component Interfaces (CPI)
> ----------------------------------------------------------
>
>                 Key: AIRAVATA-1005
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1005
>             Project: Airavata
>          Issue Type: Story
>            Reporter: Suresh Marru
>            Assignee: Suresh Marru
>             Fix For: 1.0
>
>
> As discussed in the thread - http://markmail.org/thread/tl3u2yx7tswdup24, all Airavata
Internal components should expose CPI (Component Provider Interfaces). All the components
currently have API's, SPI's in some form. But we need to enhance and streamline all these
into well defined CPI's which are exposed to clients through Airavata API facade and used
for internal component to component communication.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message