The first conclusion I've reached is that outrigger does have users, and
so learning enough about it to fix a possible concurrency bug would be
useful. I want to begin by making the current functionality work, even
under unrealistic stress. I would also like to see if maintainability
can be improved with adversely affecting performance.
I have one wish-list item of my own - an outrigger benchmark. As I make
changes, I need some way to detect and guard against performance
regression, and possibly find performance gains. As I've already said in
this mailing list, I'm a non-believer in performance tuning without
measurement.
We can certainly start a discussion on JavaSpace enhancements. I don't
promise to be able to implement them, but I'm willing to talk.
Patricia
James Grahn wrote:
My company also uses Outrigger semi-frequently.
I didn't speak up when Patricia was asking about the implementation,
because I've not dug into the actual code that much.
That said, most of my aspirations for River revolve around improving
Javaspaces. (Unfortunately with a few compatibility breaks from the
existing version.)
I'll try to pass along my wishlist soon, just so it's on the record even
if I don't get around to contributing any code. If nothing else, it
should be useful for discussion.
jamesG
On 12/3/2010 2:41 PM, Dennis Reedy wrote:
Outrigger is a key service in a project that I am involved in. I see
no reason to remove it from the distribution, it provides a solid
implementation of the JavaSpace and JavaSpace05 interfaces. There are
other services I would vote off the island ;) but thats a topic for a
different thread.
Dennis
On Dec 3, 2010, at 130PM, Tom Hobbs wrote:
With River's recent revitalization let's not deprecate anything too
hastily.
+1. You never know, this may yet convince someone who knows about
Outrigger to come back!
On Fri, Dec 3, 2010 at 6:21 PM, Jeff
Ramsdale<[email protected]> wrote:
On Fri, Dec 3, 2010 at 7:15 AM, Gregg Wonderly<[email protected]>
wrote:
Many people are using Dan Creswell's Blitz JavaSpaces
implementation or
commercial versions. I'm partially inclined to suggest that we should
discuss EOL of outrigger at some point. Even though Javaspaces is a
large
part of what Jini has been recognized for, it has a focused
audience and if
we don't have someone with knowledge and interest to support
outrigger, it
may be more of a wart than River can deal with.
With River's recent revitalization let's not deprecate anything too
hastily. Conventional wisdom in Java app development has struggled to
hold its own against NoSQL and other interesting technologies. It
could be the perfect opportunity for Jini/JavaSpaces to gain new
interest.
-jeff
