Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5AA64200C70 for ; Thu, 4 May 2017 13:06:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 595BE160BB0; Thu, 4 May 2017 11:06:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id AADBB160B9F for ; Thu, 4 May 2017 13:06:07 +0200 (CEST) Received: (qmail 87457 invoked by uid 500); 4 May 2017 11:06:06 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 87448 invoked by uid 99); 4 May 2017 11:06:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 May 2017 11:06:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 7E76B1883D6 for ; Thu, 4 May 2017 11:06:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 1sWPrH9tDi0k for ; Thu, 4 May 2017 11:06:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 85B005FC96 for ; Thu, 4 May 2017 11:06:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id F19F4E05BF for ; Thu, 4 May 2017 11:06:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1E42421DF1 for ; Thu, 4 May 2017 11:06:04 +0000 (UTC) Date: Thu, 4 May 2017 11:06:04 +0000 (UTC) From: "Pavel Tupitsyn (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-2492) .NET: Peer assembly loading MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 04 May 2017 11:06:08 -0000 [ https://issues.apache.org/jira/browse/IGNITE-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996551#comment-15996551 ] Pavel Tupitsyn commented on IGNITE-2492: ---------------------------------------- [~vozerov] I agree. Peer assembly loading should not be implemented within binary marshaller, but only enabled for particular cases. We can have a common wrapper object, {{PeerLoadingObjectHolder}}, which holds assembly information along with the object itself, and perform peer requests during deserialization if needed. This wrapper will be used only when peer loading is enabled and in places where it is applicable. > .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 > 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)