On Tue, 26 Feb 2002, marc fleury wrote: > ok, > > still jet lagged... (australia!) > > So let's imagine that we multi-thread the MainDeployer, each deployment gets > a thread. > > Each time a thread wants a class the ServiceLibraries tries and if it is a > CNFE waits. > > when a class is registered in the SL it notifiesAll threads waiting. > > voila! auto-resolving dependencies at deployment time, > > Am I delirious or is it this simple. > > marcf
Hehehe. I wrote something very similiar to this idea in shell. It was a dependency system for sysv init systems. All scripts are started in series. No changes. If an init script sees that one of its dependencies are not available, it spawned into the background, and waited. As each script got past its internal dependency check, it notified only those scripts that were waiting on itself. This required a global lock to make sure none of the lists were being modified. The notification system invovled obtaining the global lock, echoing $$(in shell, the current process id) to some file, then sleeping. When the dependant came up, it sent a signal to those processes. Multi-threaded dependency systems are very easy to implement. Child's play, even. The problem is detecting dead-locks(dependency loops, unmet dependencies), and the too-many-threads issue. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
