[
https://issues.apache.org/jira/browse/IGNITE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108329#comment-17108329
]
Marty Jones edited comment on IGNITE-7269 at 5/15/20, 2:23 PM:
---------------------------------------------------------------
I am looking to use Ignite within our Asp.Net web application and will need
distributed sessions in order to use it. I have reviewed the source for the
IgniteSessionStateStoreProvider and it doesn't look like a huge lift to create
a version for the Thin client. The only thing I am not sure about is the
"OutInOp" method for locking/releasing.
I don't mind contributing if that would help.
That being said, how large is the overhead of using the "Client" mode within an
.NET application? I would need one cache for session and one to hold items we
would cache.
was (Author: marty.jo...@newportgroup.com):
I am looking to use Ignite within our Asp.Net web application and will need
distributed sessions in order to use it. I have reviewed the source for the
IgniteSessionStateStoreProvider and it doesn't look like a huge lift to create
a version for the Thin client. The only thing I am not sure about is the
"OutInOp" method for locking/releasing.
I don't mind contributing if that would help.
> .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)
