Return-Path: X-Original-To: apmail-clerezza-dev-archive@www.apache.org Delivered-To: apmail-clerezza-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 40E4510E56 for ; Sun, 28 Jul 2013 15:29:39 +0000 (UTC) Received: (qmail 99149 invoked by uid 500); 28 Jul 2013 15:29:38 -0000 Delivered-To: apmail-clerezza-dev-archive@clerezza.apache.org Received: (qmail 99060 invoked by uid 500); 28 Jul 2013 15:29:34 -0000 Mailing-List: contact dev-help@clerezza.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@clerezza.apache.org Delivered-To: mailing list dev@clerezza.apache.org Received: (qmail 99052 invoked by uid 99); 28 Jul 2013 15:29:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Jul 2013 15:29:32 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [213.238.45.90] (HELO r2-d2.netlabs.org) (213.238.45.90) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Jul 2013 15:29:26 +0000 Received: (qmail 15419 invoked by uid 89); 28 Jul 2013 15:28:42 -0000 Received: from unknown (HELO mail-lb0-f169.google.com) (farewellutopia@netlabs.org@209.85.217.169) by 0 with ESMTPA; 28 Jul 2013 15:28:42 -0000 Received: by mail-lb0-f169.google.com with SMTP id d10so3664644lbj.28 for ; Sun, 28 Jul 2013 08:28:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=SVqB+VYDPE/DBUi+Fbmf5haCRVaTeRBQ29mIJefTbWY=; b=BVtkT3L/NCGBNGeuDSjBiDJPd+Bp1MILuCKB5RCWoCc1TxA9/xbdIojinEKvazVClc ph7vLwnT9j1mFm7yfMKqH2BKNX52Itte+D/lGS4Oq8NBSOwAamoPYUttkHJyR/SjTRr/ 1OfDegYOv/f1722qZpyH/qY99jjDlTktz8qL8uJVOt2TsCQuLieyAXCwYZzqL4C3dxil 2Xy/DisrfEinGzmn87QFbHkeF3AfIsF9lwDAYrErPhU7dJQ5d8QUB1hvUi1D0ETTnUcW Eo9NqOqpjCYkP/mqjxrlrKtBdfrdw68fUXHL/DWNu3T3xTSyRVjlMaEe9H8QCP8PQbCl l6Yw== MIME-Version: 1.0 X-Received: by 10.152.42.171 with SMTP id p11mr24821159lal.79.1375025321965; Sun, 28 Jul 2013 08:28:41 -0700 (PDT) Received: by 10.152.125.144 with HTTP; Sun, 28 Jul 2013 08:28:41 -0700 (PDT) X-Originating-IP: [31.24.10.206] In-Reply-To: References: <51E41AE3.2090906@xup.nl> Date: Sun, 28 Jul 2013 17:28:41 +0200 Message-ID: Subject: Re: Do we need Scalable and non-Scalable SingleTdbDatasetTcProvider? From: =?ISO-8859-1?Q?Reto_Bachmann=2DGm=FCr?= To: Rupert Westenthaler Cc: dev@clerezza.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQn8RvyFjGUpF4GM8YYF0360vby8vlj28tta6TeN9Nr4kXvzSNNNrq+FZQh0390PFtYjz4sD X-Virus-Checked: Checked by ClamAV on apache.org Hi Rupert I agree re. the name. IIRC you recently fixed an issue in the current SingleTdbDatasetTcProvider. Do you remember what this was about? Cheers, Reto On Tue, Jul 23, 2013 at 8:45 AM, Rupert Westenthaler wrote: > Hi all, > > I am fine with replacing the SingleTdbDatasetTcProvider with the more > advanced ScalableSingleTdbDatasetTcProvider. However I would suggest > to keep SingleTdbDatasetTcProvider as name for the component. > > best > Rupert > > On Mon, Jul 15, 2013 at 8:41 PM, Reto Bachmann-Gm=FCr = wrote: >> On Mon, Jul 15, 2013 at 5:53 PM, Minto van der Sluis wrot= e: >>> Hi, >>> >>> The SingleTdbDatasetTcProvider probably performs a little better for a >>> small number of graphs. Otherwise I see no real benefit. >> >> This seems to be a week reason for keeping those 817 lines of code. >> Maybe @Ruperts knows more reasons? >> >> Cheers, >> Reto > > > > -- > | Rupert Westenthaler rupert.westenthaler@gmail.com > | Bodenlehenstra=DFe 11 ++43-699-11108907 > | A-5500 Bischofshofen