tag:blogger.com,1999:blog-11441755.post757553094930296186..comments2024-03-28T07:56:17.809+00:00Comments on Revit : Revit tries to poison workers!!!Anonymoushttp://www.blogger.com/profile/05609028351574557112noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-11441755.post-32772757078940338462009-11-07T04:05:29.780+00:002009-11-07T04:05:29.780+00:00This is my all time favorite journal comment (and ...This is my all time favorite journal comment (and currently being incorporated into a T-shirt)! Runner up is "purgeDeletedWorksetsAndNukeGraveyard"Zach Kronhttps://www.blogger.com/profile/12789983116042927745noreply@blogger.comtag:blogger.com,1999:blog-11441755.post-65377130594548914322009-11-06T22:57:52.582+00:002009-11-06T22:57:52.582+00:00Thread Pool is a programming pattern.
The Thread ...Thread Pool is a programming pattern.<br /><br />The Thread Pool is made up of "Workers". As the application has a task to perform it lets the Thread Pool know and assigns a Worker to the task...the worker does the task and returns back to the Thread Pool.<br /><br />This is what is used to allow applications to do multiple task at once... multiple workers from the Thread Pool working on their own task concurrently.<br /><br />I am not sure, but I would assume that “Could not posionWorkers” is likely part of Revit's Thread-Safety implementation. Since the Thread Pool is busy, their must be a lock on one thread or all threads are being used and the pool can't be used/accessed (or can't be poisoned).<br /><br />This is still a funny find, and it shows that some Revit programmer has a sense of humor.Dustinhttps://www.blogger.com/profile/05991555944913246010noreply@blogger.com