concerted-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Atri Sharma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONCERTED-3) Concerted API defining
Date Mon, 19 Oct 2015 19:30:27 GMT

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

Atri Sharma commented on CONCERTED-3:
-------------------------------------

I think it is a good idea but I want this JIRA to also focus on the core API that will be
defined. It is a great idea to have a REST API also implementing the same (improves our use
case width).

Suggestions for the main interface are requested.

> Concerted API defining
> ----------------------
>
>                 Key: CONCERTED-3
>                 URL: https://issues.apache.org/jira/browse/CONCERTED-3
>             Project: Apache Concerted
>          Issue Type: New Feature
>            Reporter: Atri Sharma
>
> A decision needs to be taken on Concerted's API that will be exposed to clients.
> The API should be allowing direct access to resource managers, transaction manager, lock
manager(?) etc
> The API will help define development policy and process for adding a new resource manager
or component.



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

Mime
View raw message