Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <48BD7F3C.2080106@cox.net>
Date: Tue, 02 Sep 2008 13:00:28 -0500
From: Gregg Wonderly <gergg@cox.net>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: river-dev@incubator.apache.org
Subject: Re: Jini, JavaSpaces, JEE, some questions, and some other development
 issues and ideas.
References: <109144.74372.qm@web33802.mail.mud.yahoo.com>
 <caf30e2a0809012341i2fb0dde2y1d860e8b2ff8202a@mail.gmail.com>
In-Reply-To: <caf30e2a0809012341i2fb0dde2y1d860e8b2ff8202a@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Niclas Hedhman wrote:
> On Tue, Sep 2, 2008 at 4:23 AM, Wade Chandler
> <hwadechandler-apache@yahoo.com> wrote:
>> What I'm getting at is those TOs can hold some logic used on both sides in the situations where needed...
> 
> AFAIK, you can serialized anything into the JavaSpace. The public
> field requirement is only for what can be used to look up those
> instances later.

Yes.

> The rest of this discussion is mostly about programming patterns, and
> every developer thinks he knows better.... ;o)

Yes, and no.  Some of this is about how Jini forces particular programming 
patterns which may not seem to have obvious benefits.

There are many things which are explored in software systems design.  APIs are 
changed, and the lessons learned, never are literally communicated, only the 
APIs attempt to enforce them are visible.  Idempotent programming styles are 
very advantageous.  Finding this out can be hard until you are "forced" to 
program this way.

Gregg Wonderly