Issue 7 in israfil-micro: Components that have lifecycle should be registered with a startup timeout.

[codesite...@google.com]

Issue 7: Components that have lifecycle should be registered with a startup
timeout.
http://code.google.com/p/israfil-micro/issues/detail?id=7

New issue report by christianedwardgruber:
Components that have startup logic can spin out of control, taking the
thread forever. The
container needs a facility to optionally register a component with a
startup timeout, such that the
container will fail the startup of a given component if it (or its
dependencies) exceed their startup
timeout.

Note: timeout for each component should not encapsulate its dependencies
timeouts. This means
that "timeout" starts after dependencies are started, so if a component has
an upstream dep that
doesn't time out (wasn't registered with one), it could still spin out
waiting for its upstream
component. But if all components (with lifecycle) have a timeout, then it
should be safe.

Issue attributes:
Status: Started
Owner: christianedwardgruber
Labels: Type-Enhancement Priority-High Milestone-Release-1.2 Affects-1.1
Component-Container Performance OpSys-All

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings