Re: RunLevel Service with optional concurrency


Actually after thinking about it for a second there is no way to figure out from the Runnable passed in which service is going to be executed with it.  This may call for a small mini-feature whereby the Runnable passed to the executors also implement some other interface from which the user can get some sort of indication of which RunLevel service is about to be started.  One issue with even such an interface as that is that not all RunLevel services are started via the executor, as they may also be started by dependency map.  Basically if B depends on A and the RunLevelService decides to start B then it will find the dependency A and start it as well without going through the executor.  So that's not quite the correct solution for that.

So this may need more thought, so perhaps you should enter in an enhancement request!

Join to automatically receive all group messages.