Hi Dan,
On Nov 30, 2008, at 341PM, Dan Rollo wrote:
Hi All,
I'm in the midst of some redesign discussions with other devs on the
CruiseControl project (plug link: http://cruisecontrol.sourceforge.net/distributed/index.html)
. ;)
We have a "Distributed extension" aka: DistCC (for remote build
agents) that we are trying to merge into the core of the project. We
are also working to remove some coupling to "shared file systems"
that have limited our options going forward. Towards that end, I see
Jini as a way to keep hostname and other hardcoded network
configuration out of the picture.
In my stumblings with Jini, I've more that once done things the
"wrong way", and I think I have an opportunity to use a nice "Jini
Container" that will do things the "right way", and protect me from
myself in the future. ;)
While searching for such "Jini Service Containers", I have a few
questions about what might be the best fit:
Rio
https://rio.dev.java.net/
This is the one I've heard the most about, but I'm a little
concerned about the size of it's footprint. Any thoughts here? Are
there smaller "rio parts" that could be deployed, without requiring
a ~15mb download on each client? Even if not, it's probably not a
show stopper, but it may be harder to get buy in...
The Rio download should not be confused with the Rio distribution
requirements, it depends on what you need. Rio comes bundled with
optional third party technologies that you may not need (take a look
at the third party technologies document in the lib directory for
details on the bundled technologies , their use and licenses). For
example if you dont want Spring and it's required commons jars they
can be removed, junit does not need to be included, tools jars for
classdepandjar, etc...
Let me know if this helps or if you need more clarification. Feel free
to send mail to [EMAIL PROTECTED] if you need any assistance, or
feel free to contact me directly.
Regards
Dennis
