ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3430) .NET: Run Ignite transactions via standard TransactionScope API
Date Thu, 26 Jan 2017 15:07:24 GMT

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

ASF GitHub Bot commented on IGNITE-3430:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/ignite/pull/1407


> .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
>              Labels: .net, roadmap
>             Fix For: 1.9
>
>
> 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
> https://msdn.microsoft.com/en-us/library/ee818754(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)

Mime
View raw message