Return-Path: Delivered-To: apmail-incubator-river-dev-archive@locus.apache.org Received: (qmail 81457 invoked from network); 10 Dec 2008 03:10:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Dec 2008 03:10:00 -0000 Received: (qmail 1582 invoked by uid 500); 10 Dec 2008 03:10:13 -0000 Delivered-To: apmail-incubator-river-dev-archive@incubator.apache.org Received: (qmail 1561 invoked by uid 500); 10 Dec 2008 03:10:13 -0000 Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: river-dev@incubator.apache.org Delivered-To: mailing list river-dev@incubator.apache.org Received: (qmail 1550 invoked by uid 99); 10 Dec 2008 03:10:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Dec 2008 19:10:13 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 209.147.126.92 is neither permitted nor denied by domain of mmcgrady@topiatechnology.com) Received: from [209.147.126.92] (HELO zimbra.topiatechnology.com) (209.147.126.92) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2008 03:09:58 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.topiatechnology.com (Postfix) with ESMTP id AE8013521471 for ; Tue, 9 Dec 2008 19:09:37 -0800 (PST) X-Virus-Scanned: amavisd-new at Received: from zimbra.topiatechnology.com ([127.0.0.1]) by localhost (zimbra.topiatechnology.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RMJpcg1DhS2P for ; Tue, 9 Dec 2008 19:09:37 -0800 (PST) Received: from 113.sub-75-196-252.myvzw.com (113.sub-75-196-252.myvzw.com [75.196.252.113]) by zimbra.topiatechnology.com (Postfix) with ESMTP id 4D0273521461 for ; Tue, 9 Dec 2008 19:09:32 -0800 (PST) Message-Id: <584BFCD6-B319-4D24-A042-6B0FFD7F3A54@topiatechnology.com> From: Michael McGrady To: river-dev@incubator.apache.org In-Reply-To: <493EA11B.8000900@wizards.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v929.2) Subject: Re: Split JavaSpaces and JINI Date: Tue, 9 Dec 2008 22:09:30 -0500 References: <964EAC824495234A86F3C47DA8BD8AAD17750A@sucden-exch.sucden.co.uk> <49390F0E.7080204@dcrdev.demon.co.uk> <964EAC824495234A86F3C47DA8BD8AAD177530@sucden-exch.sucden.co.uk> <493D40A9.7020808@wizards.de> <863EA217-8B6B-4881-867E-8A645A036276@topiatechnology.com> <493D77B0.5060803@wonderly.org> <493E9460.1030901@wonderly.org> <3FD8879E-07D0-49C1-B2DC-74A630D4C0DF@topiatechnology.com> <493EA11B.8000900@wizards.de> X-Mailer: Apple Mail (2.929.2) X-Virus-Checked: Checked by ClamAV on apache.org Hello, Holger, Here is where I am coming from. I am relatively new to the more detailed issues relating to JINI and =20 JavaSpaces. I got here due to some pretty formidable issues in network computing =20 involving scaling and performance that looked like JavaSpaces could =20 definitely help. The basic ideas behind JavaSpaces made sense and =20 were not even challenging, even though exciting and I think rather deep. When I ran into the JavaSpaces and JINI mix, I was surprised at the =20 "messiness" of it all. I find that clean code that makes immediate =20 semantic sense is pretty necessary in the jobs I do. I pretty much =20 have to ensure ultraquality not unlike aerospace and nuclear power =20 plant issues. Also, I have to consider pretty severe security issues =20= and having extra functionality in a code base where it seemingly does =20= not belong becomes an issue in a heartbeat. For me the current codebase is not very usable. I would prefer to =20 have a JavaSpaces API that allowed a full use of JavaSpaces (Linda =20 spaces as it were) and to keep JINI aside for whatever extras there =20 were outside that. MG On Dec 9, 2008, at 11:47 AM, Holger Hoffst=E4tte wrote: > Michael, > > I am still not sure what exactly you would gain, in practical terms. =20= > Why > would you want to decouple the two when the individual parts are not > particularly useful without each other? This might be useful if we had > complicated build dependencies or huge jars that become too big or > cumbersome to buid/test, but none if this is the case at the moment. > >> is being discussed here is how to decouple, not a divorce. This may >> only require moving the Entry interface over to JavaSpaces. That =20 >> "plain > > Entry just marks things so now every regular service lookup would =20 > depend > on JavaSpaces? That makes no sense. The only possibility out of this =20= > might > be two different interfaces, one for Jini lookups and one for marking > space entries, but again what's the gain? It's just an interface. If =20= > you > treat the Jini core classes as "just another library" instead of =20 > like an > intimidating machinery with mobile code and whatnot, the entire =20 > issue goes > away. > I wrote my first few JavaSpaces examples and happily used some of =20 > the Jini > core classes (like remote events) without knowing one bit about the =20= > details. > >> The Javaspace API is of interest independent of JIN, as others have >> pointed outI. If River won't decouple them, then that is an =20 >> unnecessary >> limitation of the codebase which would be unfortunate for a project >> seeking interested people. > > I get the impression that somehow you really want "something else", =20= > i.e. > the functionality of JavaSpaces without Jini..? If so please explain =20= > what > and why - just curious. > > Holger Michael McGrady Senior Engineer Topia Technology, Inc. 1.253.720.3365 mmcgrady@topiatechnology.com