[
https://issues.apache.org/jira/browse/IGNITE-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020046#comment-16020046
]
Vladimir Ozerov commented on IGNITE-2492:
-----------------------------------------
[~ptupitsyn],
I walked through the code. While this is definitely an interesting feature,
without a clean and consistent lifecycle of a loaded domain I doubt we can
include it into the product.
How difficult would it be to apply domain-based approach? It seems that with
help of some fine-tuning we can force .NET to share Ignite classes between
domains [1], so that there will be not so much cross-domain calls.
[1]
https://stackoverflow.com/questions/15414791/full-asp-net-style-appdomain-assembly-isolation
> .NET: Peer assembly loading
> ---------------------------
>
> Key: IGNITE-2492
> URL: https://issues.apache.org/jira/browse/IGNITE-2492
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .net, important
> Fix For: 2.1
>
>
> Similar to peer class loading in Java, we can provide a possibility to load
> assemblies on already started nodes, so that a node can execute jobs that are
> not present on other nodes.
> Considerations:
> * Can we unload assemblies after use to free memory? This requires a separate
> AppDomain, can we work with that?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
