You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@airavata.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/05/26 05:44:17 UTC

[jira] [Commented] (AIRAVATA-1701) Deprecate client and server execution modes

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

ASF subversion and git services commented on AIRAVATA-1701:
-----------------------------------------------------------

Commit a23a9cc01587d3326a3119a8b201fcd6c7d33f1d in airavata's branch refs/heads/master from [~smarru]
[ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=a23a9cc ]

Removing the legacy server vs client mode - AIRAVATA-1701


> Deprecate client and server execution modes
> -------------------------------------------
>
>                 Key: AIRAVATA-1701
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1701
>             Project: Airavata
>          Issue Type: Task
>            Reporter: Suresh Marru
>            Assignee: Suresh Marru
>
> As a legacy API artifact, some of the classes in Airavata were reused both in clients and server modes. With thrift services, these issues are not relavant and the util classes can be deprecated. All the checks for server vs clients should be removed. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)