On Thu, Jan 15, 2009 at 11:11 AM, Ben Goodger (Google) <b...@chromium.org>
wrote:
> I'm not coming at this from an optimization perspective, I'm thinking
> more of making the startup flow understandable to mere mortals.
Amanda's suggestion would likely actually accomplish both, so I don't
think we should dismiss it if it happens to make startup faster as a
result as well. :-)
The gist would be to have some way for a given service to specify its
startup dependencies. Once you do that, then you can essentially list
your startup services in pretty much any order since the dependencies
would get worked out correctly. It would also allow us to catch
things like dependency cycles and to more clearly figure out how to
optimize startup time by perhaps figuring out how to remove
unnecessary dependencies. Finally, it would allow easier unit testing
since you'd be able to safely grab a subset of the services you want
to test and to have a system that knows how to initialize properly
(addressing Scott's issue).
Of course, coming up with a nice way to express these dependencies
cleanly and actually figuring out what all of the dependencies are are
both easier said than done.
Erik
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
