Return-Path: Delivered-To: apmail-james-server-dev-archive@www.apache.org Received: (qmail 24381 invoked from network); 21 Nov 2005 12:44:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Nov 2005 12:44:41 -0000 Received: (qmail 63381 invoked by uid 500); 21 Nov 2005 12:44:40 -0000 Delivered-To: apmail-james-server-dev-archive@james.apache.org Received: (qmail 63345 invoked by uid 500); 21 Nov 2005 12:44:39 -0000 Mailing-List: contact server-dev-help@james.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "James Developers List" Reply-To: "James Developers List" Delivered-To: mailing list server-dev@james.apache.org Received: (qmail 63334 invoked by uid 99); 21 Nov 2005 12:44:39 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Nov 2005 04:44:39 -0800 Received-SPF: pass (asf.osuosl.org: domain of danny.angus@gmail.com designates 66.249.82.196 as permitted sender) Received: from [66.249.82.196] (HELO xproxy.gmail.com) (66.249.82.196) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Nov 2005 04:46:12 -0800 Received: by xproxy.gmail.com with SMTP id i26so650688wxd for ; Mon, 21 Nov 2005 04:44:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sYfHVF7MpBZuNSnkhiyJtxQsGi6GtPc8iLxKDT5uVf6JG7PENDnQJZlJ/xjio4LQjVXdeKqG8SYHoQZ0qZFUBzeoWxdXip39VsNei+Do0zKKe4CtIu0gsBfJ3oY0pOKlV+Jz7sGbc86EokCd6loEG68GT7lOA0Nnhw/BiH7EMlM= Received: by 10.64.251.9 with SMTP id y9mr2806324qbh; Mon, 21 Nov 2005 04:44:18 -0800 (PST) Received: by 10.65.15.9 with HTTP; Mon, 21 Nov 2005 04:44:17 -0800 (PST) Message-ID: <5ec229170511210444w16c50e75t@mail.gmail.com> Date: Mon, 21 Nov 2005 12:44:18 +0000 From: Danny Angus Reply-To: danny@apache.org To: James Developers List Subject: Re: Problems using Derby for stores In-Reply-To: <437E20E0.7020605@debrunners.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <437E20E0.7020605@debrunners.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 18/11/05, Daniel John Debrunner wrote: > Noel J. Bergman wrote: Noel, I wasn't suggesting that we deprecate file-stores, but they *would* become more of a niche, and probably used mainly for interoperability with software which expects one of the common mail file formats. > > I'm not quite sure what that would mean to embed JAMES. ... > I probably mean, embed some of JAMES's services in Derby. I liked this, and thought of it not as locking James into derby to support one or more services, but as an alternate implementation of a service. You could then lever all the power available from Derby to make James fly in certain popular configurations (read this as "for key target market segments"). For instance a "DebySpoolManager" might make good use of triggers, and perform really smoothly, a "DerbyMailStore" could have a custom type in the db that *was* a MimeMessage, and a custom function to return its size in bytes. Just my 2c though.. d. --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org For additional commands, e-mail: server-dev-help@james.apache.org