|
![]() |
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Originally posted by Mr. C Lamont Gilbert:
why does it matter which thread runs the code? That should be abstract.
Command pattern or strategy is good way to allow a thread to run different code at different times.
Originally posted by Ken Blair:
I'm working with COBOL files and in order to open a new connection to a file it must be done in a new Thread. The fun part comes when I have to keep that Thread alive and wait for further requests to be made on that file.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
From the API:
This interface provides a way of decoupling task submission from the mechanics of how each task will be run, including details of thread use, scheduling, etc
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |