On Tue, 2010-05-25 at 13:20, Dennis Reedy wrote: > On May 25, 2010, at 1156AM, Patrick Wright wrote: > > I myself would just > > like to see River move away from the idea that dynamic download via > > codebase services is a requirement, more or less, of using Jini, and > > to provide a reasonable/workable alternative for those that don't need > > it. > > Sums up the entire impetus to this thread, well said!
Just curious, here... Dynamic loading of proxy classes has always seemed (to me) to be at the core of the Jini philosophy. Much of the dynamic discovery, dynamic redeployment, the concepts in Jim Waldo's "The End of Protocols" (http://java.sun.com/developer/technicalArticles/jini/protocols.html), Frank Somers' "Survival of the Fittest Jini Services" (http://www.javaworld.com/javaworld/jw-04-2001/jw-0413-jiniology.html), etc, goes away if you take out dynamic proxy loading. So what's the downside of dynamic download, specifically? I can see the issue in a bandwidth limited situation (which is actually not Jini's original target, but could probably be handled with sufficiently bright jar caching), but in a well-connected local area network environment (Jini's design center) what problems do we face, and might there be simpler ways to handle them? Cheers, Greg. -- Greg Trasuk, President StratusCom Manufacturing Systems Inc. - We use information technology to solve business problems on your plant floor. http://stratuscom.com
