river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Firmstone <j...@zeus.net.au>
Subject Re: [Was: OSGi and Jini] Now -> Next Steps
Date Sat, 04 Jul 2009 00:22:05 GMT
Dennis Reedy wrote:
> Forget about OSGi for now, its a red herring for River moving out of 
> incubation, and frankly a bit of noise that produces the same reaction 
> every time it is posted. This is not to say the each technology 
> (combined or separate) does not have its merits/issues, its just time 
> to move on.
> How about AR2 gets released? Take the current project structure and 
> tests, and release what you have. I think its a safe bet to say that 
> the trunk represents a stable production worthy technology (AR1 
> certainly is). If there is more wok to do with the testing framework, 
> fine. Then release AR3 shortly there-after. I'll be glad to upload the 
> package name changes from com.sun.jini to org.apache.river as well if 
> the timing is right post AR2.
That's almost the plan, just want to get all the tests right first and a 
couple of tweaks to the build then release.  It's almost ready, I've 
just been very busy and haven't gotten onto it yet.  Not much work left 

On that subject, I'm having some trouble deciding on a solution to 
replace the Squid proxy server that was present on Sun's network?  Any 


> On Jul 3, 2009, at 1125AM, Sam Chance wrote:
>> Well said, Jukka!
>> Gregg, I say you do something with Jini and OSGi.  :-)  Seriously, what
>> about a semantic LUS?  Build a way to query for Services using Semantic
>> technologies like RDF and SPARQL.  Or use Jini to manage distributed 
>> OSGi
>> bundles (RDF 119 is Distributed OSGi). Or build an AJAX front-end for
>> lifecycle management of Jini federations and services.
>> Just some thoughts.
>> On Fri, Jul 3, 2009 at 5:26 AM, Jukka Zitting 
>> <jukka.zitting@gmail.com>wrote:
>>> Hi,
>>> On Mon, Jun 29, 2009 at 10:20 PM, Gregg Wonderly<gregg@wonderly.org>
>>> wrote:
>>>> What happens next is what the community decides.  I'd like to play a
>>> part,
>>>> but to date, everything that I've found to be interesting and 
>>>> wanted to
>>> do
>>>> differently in Jini has not been that interesting to the rest of the
>>>> community.
>>> Does it matter? Apart from the the test suite there currently is no
>>> active work being done on River trunk. Anyone with the energy to back
>>> up his or her proposals with solid patches gets to decide where River
>>> is going. If others don't agree, they'll need to come up with
>>> alternative patches that solve the same issues.
>>>> So, I'm setting back, waiting for something to start rolling that I am
>>>> interested in, and I'll jump in to assist as best I can, as I am 
>>>> needed.
>>> That's the wrong attitude. Just get started and others will follow! At
>>> Apache those who do, decide.
>>> BR,
>>> Jukka Zitting
>> -- 
>> Sam Chance
>> 443-694-5293 (m)
>> 410-694-0240 x108 (o)

View raw message