Return-Path: Delivered-To: apmail-incubator-ace-dev-archive@minotaur.apache.org Received: (qmail 46195 invoked from network); 7 Oct 2009 08:32:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Oct 2009 08:32:41 -0000 Received: (qmail 98676 invoked by uid 500); 7 Oct 2009 08:32:41 -0000 Delivered-To: apmail-incubator-ace-dev-archive@incubator.apache.org Received: (qmail 98645 invoked by uid 500); 7 Oct 2009 08:32:41 -0000 Mailing-List: contact ace-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ace-dev@incubator.apache.org Delivered-To: mailing list ace-dev@incubator.apache.org Received: (qmail 98635 invoked by uid 99); 7 Oct 2009 08:32:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Oct 2009 08:32:41 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tonit.com@googlemail.com designates 209.85.210.193 as permitted sender) Received: from [209.85.210.193] (HELO mail-yx0-f193.google.com) (209.85.210.193) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Oct 2009 08:32:30 +0000 Received: by yxe31 with SMTP id 31so1414421yxe.21 for ; Wed, 07 Oct 2009 01:32:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=AHMsqKrTKlQ6mYj05nRM6EwuwBg55xzGACRzSFyBJaQ=; b=a+htuUNonLC3mndeNSzDuW7uKHC8RqcgvXc3SJ28Z6k8SI6N32jFfT0oKpqAUH8zeO gDIBBC+Eixrzew5YLCSeONpXp4/HLpd3XnvWjmiVTA9UuFoqqQ7HOVo+ZioxW1Wl4bhd B+Uso5dNpAXKiGtAElOmzkIxG7bhtqDZecLII= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=cDiGqc1VuLrqEtebiG1FOCIYy4FGpgEemaF/A/EgcmrdEF9veC8fCM6cyBsZE0+hEt QUIxbvlbhKJCBU3uJK2yGUd04way0cwtgkP5IOvTYL+wwgCkfYenA6q7qq7QYZjd4p7m s3p4PToQRWNFTnmcSp1yNp/7rKGMm+JkAbWdI= MIME-Version: 1.0 Sender: tonit.com@googlemail.com Received: by 10.100.80.7 with SMTP id d7mr2716069anb.43.1254904328834; Wed, 07 Oct 2009 01:32:08 -0700 (PDT) Date: Wed, 7 Oct 2009 10:32:08 +0200 X-Google-Sender-Auth: 868075e89e01bc77 Message-ID: Subject: Installable Units in Ace From: Toni Menzel To: ace-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=0050450175fabf50900475542e26 X-Virus-Checked: Checked by ClamAV on apache.org --0050450175fabf50900475542e26 Content-Type: text/plain; charset=ISO-8859-1 Is there in ace already a concept of "installable units" (p2 terminology) ? Speaking of the fact that, if i make a group and assign it to a certain gateway (through license), does the server know about the gateways capabilities so it can make sure things are resolving ? To me this would be a crucial concept, not because its coming from p2 but to at all allow to automatically resolve dependencies for a group. (for example). Sure, because every gateway can be different, it is hard to manage this if features are assembled on the server (web ui: clicking the triangle bundle) and not on the gateway. Any thoughts already in this direction ? -- Toni Menzel Independent Software Developer Professional Profile: http://okidokiteam.com toni@okidokiteam.com http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. --0050450175fabf50900475542e26--