No Peter Pan objects
From CSSEMediaWiki
(Difference between revisions)
(→Solutions) |
|||
| Line 1: | Line 1: | ||
| + | ---- | ||
| + | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
| + | ---- | ||
| + | =[http://itygeligub.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]= | ||
| + | ---- | ||
| + | =[http://itygeligub.co.cc CLICK HERE]= | ||
| + | ---- | ||
| + | </div> | ||
Do not create something that lives forever and lose track of it. | Do not create something that lives forever and lose track of it. | ||
Revision as of 06:30, 24 November 2010
Do not create something that lives forever and lose track of it.
When creating objects that may linger indefinitely especially those who have their own resident thread always keep a reference. For purposes such as pausing a program's execution it is vital to have a handle to each object that may have a separate execution path.
Solutions
- Chain of responsibility - Make each object responsible for passing thread control messages to any children it instantiated.
- Singleton - Create a thread registry, this will contain methods to construct a new thread for a client and maintain a list of threads that have been constructed. This way the registry can directly manage the execution state of threads.
