Hi Folks, Many years ago I had a friend who spent some time telling me about "how cool" Jini was, but I never really got around to investigating it for myself at that time. Several years ago I was thinking of a project and remembered what he sad and read the Jini specs. They struck me as something that should have been much more successful than they were. They really look like they solve a lot of key problems, and I started playing a little bit and decided I probably wanted to use river. However in the way that side projects often do, it fell victim to work schedules etc. Lately, I've been reviving the project and now I've got a collaborator and a very rudimentary 0.1 release. The primary concern I've heard every time I mention Jini to anyone is the perception that it's old, done, yesterday, dying etc. Having been lurking on this list for the last couple years I can say that releases still happen and it's "Not Dead Yet" (in my best Monty Python voice) but I also can't honestly say it's very lively either. Help me counter the nay sayers :)
I've laid out my reasoning for why it fits with what I want to do in the link below and I'd like to invite anyone who actually uses Jini regularly to do any of the following: 1. Confirm that my concept/ideas/goals fit well with Jini 2. Tell me I'm crazy and I don't get it :) (nicely) 3. Say something somewhere in between 1 and 2... 4. Encourage me to use Jini 5. Discourage me from using Jini 6. Propose alternative technologies 7. *Help me build the **Jini parts of my project* :) I've started an issue in my Github repository to describe the way I plan to use Jini and host discussion about pros/cons of this choice so if you're interested you can find it here: https://github.com/nsoft/jesterj/issues/20 I also hope that if this project succeeds it might serve to re-publicize jini a bit and bring it back into the attention sphere of some of the larger open source software community... Best, Gus
