It may not be dependency injection, but enabling an in-dependency-graph-order traversal of Services, and starting them each before anything it depends on, and parallizing startup - that seems like something that can benefit from the dependency graph. Yes, it's not in the scope of the core of Guice - dependency injection, but it's not just injection, it's dependency management - injection is the core (constructing with dependencies) but if a dependency needs to be both extant/present AND properly started, the thing that controls the wiring should be helping out here.
On Mar 14, 2012, at 2:58 PM, [email protected] wrote: > > Comment #80 on issue 62 by [email protected]: Lifecycle support > http://code.google.com/p/google-guice/issues/detail?id=62 > > Services should start in the proper order - all dependencies should start > before. Same for stop. So it's really close to dependency injection. > > -- > You received this message because you are subscribed to the Google Groups > "google-guice-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-guice-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "google-guice-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice-dev?hl=en.
