> On Tue, 2006-04-18 at 08:10 +0100, Steve Ross-Talbot wrote:
> >
> > I think this is what Sanjiva is really talking about and alas this is
> > where the herd
> > risk mentality comes in. If Sun had seen fit to back it a few years ago
> > then it [Jini/JavaSpaces]
> > would probably be a more serious player. Shame that they chose not to
> > do so.
>
> Rumour has it that they're thinking about donating Jini to Apache ...
It's not really "donating." Jini will be proposed as an Apache project and go
through all of those steps. This is all part of the move by the community to
get Sun's contributed implementation to be more open in terms of developers who
have access to it. It also puts the platform into an environment where
distributed computing activities are starting to get more lively, and thus can
provide easier access to it for those who don't really have experience or
knowledge of Jini.
The Jini community has operated for many, many years as a stable and democratic
community, much in the way that Apache is viewed. The Jini community as a whole
votes on the "standards". Sun, as one of the contributors of specification
implementation, provided the Jini technology starter kit as one implementation
of the total spec. As some are aware, there have been several Javaspaces
implementations that others have done, per the spec.
Sun's engineers are being redirected to actually deploy Jini technologies into
the business (RFID project, sun research on massive information network scaling,
and other business opportunities it sounds like). So, they'd like to make sure
that the community can keep moving along. Thus, jini.org, which they pay for
and is under their control, is not longer a good match for the communities home.
If the Jini technology starter kit (JTSK) is accepted as an Apache project, then
we'll have a place for the whole community to participate in the development of
the technologies. I am working on creating a Jini community at java.net, which
will allow more visibility there of the communities activities with the "use" of
Jini technologies.
> IMO too little too late for market dominance, but it does help address
> some of the openness concerns.
Jini is not about "market dominance for those who are business centric. Jini is
about distributed computing. If you want to build large scale, distribute
systems that are self healing, Jini technologies such as the Rio platform, can
make your life so much easier. If you want to make sure that your shop can talk
everyone in the world speaking one language, Jini technologies allow you to plug
in WS-* technologies at the transport layer so that your systems can do that.
But you might also use a mediator service that is Jini on one side and WS-* on
the other.
> Anyway, I look forward to having interesting discussions and experiments
> in Apache on ways to mix and match Jini & WS-*.
There are lots of things that are going to happen to make Apache and Jini occur
together in more sentences, it seems to me.
Gregg Wonderly
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
