[
https://issues.apache.org/jira/browse/IGNITE-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820714#comment-15820714
]
Pavel Tupitsyn edited comment on IGNITE-2492 at 1/12/17 12:14 PM:
------------------------------------------------------------------
Initial implementation proposal:
* Do not bother with unloading. Load assemblies in current AppDomain.
* Load assemblies by type name. If we get an object with unknown type, send
peer loading request with that type name.
* Use existing .NET mechanisms to send requests to other nodes (send a closure
to all nodes one by one)
There are two cases:
* Binarizable types. TypeId is known, but type can't be resolved in loaded
assemblies.
* Serializable types. In this case we should handle assembly resolve event.
was (Author: ptupitsyn):
Initial implementation proposal:
* Do not bother with unloading. Load assemblies in current AppDomain.
* Load assemblies by typeId. If we get an object with unknown typeId, send peer
loading request with that typeId.
* Use existing .NET mechanisms to send requests to other nodes (send a closure
to all nodes one by one)
> .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, roadmap
> Fix For: 2.0
>
>
> 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.4#6332)
