Return-Path: X-Original-To: apmail-incubator-directmemory-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-directmemory-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BAA7F72AF for ; Mon, 10 Oct 2011 19:36:07 +0000 (UTC) Received: (qmail 80792 invoked by uid 500); 10 Oct 2011 19:36:07 -0000 Delivered-To: apmail-incubator-directmemory-dev-archive@incubator.apache.org Received: (qmail 80772 invoked by uid 500); 10 Oct 2011 19:36:07 -0000 Mailing-List: contact directmemory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: directmemory-dev@incubator.apache.org Delivered-To: mailing list directmemory-dev@incubator.apache.org Received: (qmail 80764 invoked by uid 99); 10 Oct 2011 19:36:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Oct 2011 19:36:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of daniel.manzke@googlemail.com designates 209.85.215.175 as permitted sender) Received: from [209.85.215.175] (HELO mail-ey0-f175.google.com) (209.85.215.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Oct 2011 19:36:02 +0000 Received: by eyd9 with SMTP id 9so1227775eyd.6 for ; Mon, 10 Oct 2011 12:35:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=0cXxqErOJC+MTvAe6qj/VXaPrJsAK1adhzYV1AeBiUI=; b=aewwkCICZCO+V6yVnPKRzGXJn10NbGxU1TrTTYd8ulBsd1H3XmvSTUwe1l+20ny/Eo QuDiz8LWtLeTYIWkob9u2dM1xYIVhAwDBAtAP2ceduRNkXoVFGYlUQ9+wwdNmfj0716Y H+9I7ljrYpDym/s3Af+lypjL3VPV1/bIdlJ4Y= Received: by 10.213.29.211 with SMTP id r19mr1043550ebc.77.1318275341146; Mon, 10 Oct 2011 12:35:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.35.80 with HTTP; Mon, 10 Oct 2011 12:35:21 -0700 (PDT) In-Reply-To: References: From: Daniel Manzke Date: Mon, 10 Oct 2011 21:35:21 +0200 Message-ID: Subject: Re: Initial roadmap discussion To: directmemory-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=0015174c18be6cdfba04aef6e5eb --0015174c18be6cdfba04aef6e5eb Content-Type: text/plain; charset=UTF-8 Hmmm sounds interesting. There are a lot of Frameworks using this approach. (for example Hazelcast too) The Problem of the two approaches is, that it can lead to several problems. For Example I have used in one of my Samples the Hazelcast Singleton-Methods. The Problem was, that it forced to configure the Instance itself. From that I took an Instance, which I tried to configure afterwards and this has failed. So I had to switch all usage of Hazelcast. (still it was stupid by my own, but such things can lead to problems - Hazelcast has three different ways to get an instance...) I'm totally agree, that it should not be bound to a specific DI. I kicked a lot of Integrations from my Stacks, because they forced to use Spring. (like a lot of Apache Projects...) The Projects now have to investigate a lot of Energy to separate them from the DI Frameworks. (Camel, Felix, Karaf, ...) One Sentence to the Fluent-APIs. I really like them, but they also have one problem, it is hard to use them in a dynamic Environment. You will see in the Main Implementation a lot of IF-THEN-ELSE, because they want to make it configurable. Bye, Daniel --0015174c18be6cdfba04aef6e5eb--