[jira] [Updated] (IGNITE-3430) .NET: Run Ignite transactions via standard TransactionScope API

["Pavel Tupitsyn (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Tupitsyn updated IGNITE-3430:
-----------------------------------
    Description: 
Automatically enlist Ignite operations in current transaction scope when applicable (when cache is transactional).

https://msdn.microsoft.com/en-us/library/system.transactions.transactionscope(v=vs.110).aspx

This boils down to implementing {{IEnlistmentNotification}} and calling {{Transaction.Current.Enlist}} when doing transactional operations.

Later we may want to implement {{ISinglePhaseNotification}} which is an optimization.

  was:
Automatically enlist Ignite operations in current transaction scope when applicable (when cache is transactional).

https://msdn.microsoft.com/en-us/library/system.transactions.transactionscope(v=vs.110).aspx


> .NET: Run Ignite transactions via standard TransactionScope API
> ---------------------------------------------------------------
>
>                 Key: IGNITE-3430
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3430
>             Project: Ignite
>          Issue Type: New Feature
>          Components: platforms
>    Affects Versions: 1.6
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>              Labels: .net, roadmap
>             Fix For: 2.0
>
>
> Automatically enlist Ignite operations in current transaction scope when applicable (when cache is transactional).
> https://msdn.microsoft.com/en-us/library/system.transactions.transactionscope(v=vs.110).aspx
> This boils down to implementing {{IEnlistmentNotification}} and calling {{Transaction.Current.Enlist}} when doing transactional operations.
> Later we may want to implement {{ISinglePhaseNotification}} which is an optimization.



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