Mailing-List: contact dev-help@falcon.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.incubator.apache.org
Date: Thu, 18 Sep 2014 18:41:34 +0000 (UTC)
From: "Ajay Yadav (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12739094.1409826070000.68309.1411065694224@Atlassian.JIRA>
In-Reply-To: <JIRA.12739094.1409826070000@Atlassian.JIRA>
References: <JIRA.12739094.1409826070000@Atlassian.JIRA>
 <JIRA.12739094.1409826070885@arcas>
Subject: [jira] [Commented] (FALCON-672) Design/Implement the client /server
 api
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ajay Yadav commented on FALCON-672:
-----------------------------------

One small suggestion, Can we have more succinct and nemonic names for the Designer Interface e.g.
list, get, validate, submit, delete, save and deploy etc. ?

> Design/Implement the client /server api
> ---------------------------------------
>
>                 Key: FALCON-672
>                 URL: https://issues.apache.org/jira/browse/FALCON-672
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: designer
>            Reporter: samar
>         Attachments: falcon_desinger_api_design.jpg, flow_object_model.jpg
>
>
> Design/Implement the client /server api which will be exposed by the server and will be used by any client to interact with designer. This would include the final data model and the service contract


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