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] [Commented] (AIRAVATA-1005) Rename and Enhance the Airavata Component Interfaces (CPI)
Date Fri, 21 Feb 2014 13:01:20 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908268#comment-13908268
] 

Suresh Marru commented on AIRAVATA-1005:
----------------------------------------

As the CPI's are evolving, integrating them into various components is warranting initiating
the components, setting the constructors and especially non-blocking calls creating lot of
objects in memory. How about we let the thrift services penetrate to these components and
move foreword with CPI level thrift service?

I will assume lazy consensus and prototype the registry CPI as a service, meanwhile lets please
discuss the alternatives. 

> 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
>
> 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.1.5#6160)

Mime
View raw message