Re: River and Backward Compatibility

I belong to the posse of 'slient members' of this community.
While I don't work with a committed Jini/JavaSpaces shop, I
try to (and have succeeded a couple of times) to generate
some palpable interest about the subject and its promises, in the
minds of men who matter. This makes me remain a silent watcher of
the conversations happening in the ring most of the time, and
allows me to infrequently install and run some PoC using the
latest version to prove a point or write a white-paper for my
employers.

Having said all these, I must also add that forking at the
River (desperate attempt to sound poetic) is something we all
should avoid and prevent. In any case, JavaSpaces does not hold
that much of mind-share in the development community world over,
as much we would like to. Forking will drag the subject into
unnecessary controversy and may engender some to jump the ship.

In this light, keeping backward compatibility is a necessity, I feel;
unless of course, that is leading to meaningless complexity. Let's
face it: to an average JavaSpaces enthusiast, tweaking the software
is not an easy job. I would guess that by safeguarding the backward
compatibility, we would help such people.

My 0.5 cents, and Brian++ (+2, that is), from me.

Nirmalya
Pune
India
*************************** ADVERTISEMENT ******************************
Get BT Broadband from only EUR20 per month! Always-on internet
& wireless option - find out more at http://www.btireland.ie/broadband

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html