[Registry-dev] Transaction support in the registry

[Chathura C. Ekanayake]

Yes, we may have to use some special headers to specify batch messages.

But APP can also simply call beginTransaction() in one message. Then 
perform all transactional operations in multiple messages. And call 
commit() in another message. That way, we can introduce transactions to 
APP interface with minimum changes to the protocol.

But I agree that we should also support batch mode in APP.

Thanks,
Chathura

Paul Fremantle wrote:
> Sure, but how do you batch up the operations into a single APP call?
>
> Paul
>
> Chathura C. Ekanayake wrote:
>>
>> +1. I am already implementing transaction functionality in the 
>> JDBCRegistry. We can introduce transactional methods to the API.
>>
>> registry.beginTransaction();
>> registry.rollback();
>> registry.commit();
>>
>> Once these methods are added to the JDBCRegistry, APP interface can 
>> simply call these methods to perform set of actions remotely within a 
>> transaction.
>>
>> Thanks,
>> Chathura
>>
>> Paul Fremantle wrote:
>>> +1 from me. We discussed this initially, and I think it makes some 
>>> sense.
>>>
>>> I guess we have a challenge when it comes to APP though. (Maybe some 
>>> funky header extensions?). How does SVN do this?
>>>
>>> Paul
>>>
>>>
>>>
>>> Afkham Azeez wrote:
>>>> https://wso2.org/jira/browse/REGISTRY-265
>>>>
>>>> In Carbon, when a service is deployed, we store service meta data 
>>>> in the registry. These are added as several resources (policies, 
>>>> parameters, properties etc.) If something goes wrong, stale data 
>>>> should not remain in the registry. So we should be able to rollback.
>>>>
>>>> Azeez
>>>>
>>>> Sanjiva Weerawarana wrote:
>>>>> What scenario is motivating this feature?
>>>>>
>>>>> Sanjiva.
>>>>>
>>>>> Deepal Jayasinghe wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> I think is it very useful to have the transaction support in the 
>>>>>> registry API level. There will be many instances where we want to 
>>>>>> do transaction like functions in the registry , something like
>>>>>> - Create a resource
>>>>>> - rate that
>>>>>> - Comment on that and etc..
>>>>>>
>>>>>> And one of those operation fails then need to rollback all those 
>>>>>> operations. I know we can do that at the JDBCRegistry level with 
>>>>>> minor changes but it would be great if we can add the 
>>>>>> transaction  handling support in to the registry API , then 
>>>>>> anyone using APP also get the advantage of the transaction support.
>>>>>>
>>>>>> Thank you!
>>>>>> Deepal
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Registry-dev mailing list
>>>>>> Registry-dev at wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>>>>>>
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Registry-dev mailing list
>>>> Registry-dev at wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>>>>
>>>
>>
>>
>> _______________________________________________
>> Registry-dev mailing list
>> Registry-dev at wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>>
>