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 073E210DE0 for ; Mon, 15 Jul 2013 13:48:20 +0000 (UTC) Received: (qmail 93072 invoked by uid 500); 15 Jul 2013 13:48:19 -0000 Delivered-To: apmail-clerezza-dev-archive@clerezza.apache.org Received: (qmail 93022 invoked by uid 500); 15 Jul 2013 13:48:19 -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 93014 invoked by uid 500); 15 Jul 2013 13:48:18 -0000 Delivered-To: apmail-incubator-clerezza-dev@incubator.apache.org Received: (qmail 93011 invoked by uid 99); 15 Jul 2013 13:48:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jul 2013 13:48:18 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= X-Spam-Check-By: apache.org Received-SPF: error (athena.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; Mon, 15 Jul 2013 13:48:11 +0000 Received: (qmail 26844 invoked by uid 89); 15 Jul 2013 13:47:30 -0000 Received: from unknown (HELO mail-lb0-f180.google.com) (farewellutopia@netlabs.org@209.85.217.180) by 0 with ESMTPA; 15 Jul 2013 13:47:30 -0000 Received: by mail-lb0-f180.google.com with SMTP id o10so9411648lbi.39 for ; Mon, 15 Jul 2013 06:47:29 -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:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=NnYTTKEPSnf3jIrOxT3w+SuL2r8af/HhCZ5G7xQcDTc=; b=G8/OMoS4hQbkbrJKvB3CU1PT2VnITtj6Qw+d6RJK3ZdcevSDoKU3OFq2o/RnypenA3 VxtVhHUMx7alhmsNeYFd9BC67gO+NzMHy+1YKXpM38ckiFBuJ3DvmxKIZ2s4rOquQb2D FGFBs04O09cdtPyeOEfF8UuzhPf5fAQkOED3j8V9mob9mVbM4CRT2BBhP0spfZsT27G0 VWFv4n4HfO7U0GsAJQD+J8K3bFrYHsRrd1JPvQNnj3RqtWpp4AT/ZNpzvT+0DyBw8OOn QjHQFGLa9pzYQbKlMfir45opW+ekN9/TOvuuD7T+I5av7o9soZnApAzLaKzFG0NDsXfq y9JA== MIME-Version: 1.0 X-Received: by 10.112.42.44 with SMTP id k12mr24404105lbl.63.1373896049522; Mon, 15 Jul 2013 06:47:29 -0700 (PDT) Received: by 10.152.125.144 with HTTP; Mon, 15 Jul 2013 06:47:29 -0700 (PDT) X-Originating-IP: [31.24.10.206] Date: Mon, 15 Jul 2013 15:47:29 +0200 Message-ID: Subject: Do we need Scalable and non-Scalable SingleTdbDatasetTcProvider? From: =?ISO-8859-1?Q?Reto_Bachmann=2DGm=FCr?= To: "clerezza-dev@incubator.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQm/7Mm0x5y5lkBup9K7tjZ8w6gyNcor2QzwXaLrcPJXIRWP1QVc4ebCZK2y4cDIwJl0qE/q X-Virus-Checked: Checked by ClamAV on apache.org Hello As some refactoring is needed to correctly support the default graph I'm wondering what's the justification for having 2 SingleTdbDatasetTcProvider. I understand ScalableSingleTdbDatasetTcProvider works better for large number of graphs, but what are the advantages of the original one? Cheers, Reto