[
https://issues.apache.org/jira/browse/IGNITE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108940#comment-17108940
]
Pavel Tupitsyn edited comment on IGNITE-7269 at 5/16/20, 9:06 AM:
------------------------------------------------------------------
[[email protected]]
> do you know when explicit lock support will be added into the .NET thin client
Transactions are coming to .NET thin client soon. However, existing ASP.NET
session store does not use Ignite locks or transactions. `OutInOp` that you see
in code invokes PlatformDotNetSessionLockProcessor on Java side. From Thin
Client you can invoke the same processor using Compute (IGNITE-13001).
But it would be cleaner to use Transactions, I think (IGNITE-7369).
was (Author: ptupitsyn):
[[email protected]]
> do you know when explicit lock support will be added into the .NET thin client
Transactions are coming to .NET thin client soon. However, existing ASP.NET
session store does not use Ignite locks or transactions. `OutInOp` that you see
in code invokes PlatformDotNetSessionLockProcessor on Java side. From Thin
Client you can invoke the same processor using Compute (IGNITE-13001).
> .NET: Thin ASP.NET Session State Store Provider
> -----------------------------------------------
>
> Key: IGNITE-7269
> URL: https://issues.apache.org/jira/browse/IGNITE-7269
> Project: Ignite
> Issue Type: New Feature
> Components: platforms, thin client
> Reporter: Pavel Tupitsyn
> Priority: Major
> Labels: .NET, ASP.NET
>
> IGNITE-3199 introduced session store provider which works via full .NET API
> that starts JVM in process.
> Introduce {{IgniteThinSessionStateStoreProvider}} that uses thin client API.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
