Welcome to MSDN Blogs Sign in | Join | Help

A customer question on Thread.Name

A query was raised by Ilya Ryzhenkov on Thread.Name:
"What's the reason of Thread.Name property be write-once?"
Ilya, the response I got was from Chris Brumme, an architect on the CLR team. Chris points out that if you care about the name of your thread, it's worthless unless it's stable. In which case, the creator of the thread gets to make the call: do I care, or not? If you do you give it a name, and no-one else is allowed to do anything after that, in order to ensure it's stability and consistency.
Published Tuesday, November 11, 2003 7:56 PM by BCLTeam
Filed under:

Comments

Wednesday, November 26, 2003 5:01 AM by Olivier Le Pichon

# RE: A customer question on Thread.Name

Yes but if you want to reuse a thread to do different kind of job (à la ThreadPool) it can be great to be able to modify its name.
Tuesday, June 10, 2008 4:43 PM by Blog d'Olivier Huet

# Nommer ses threads, mais une seule fois !

Pour des besoins de diagnostic, il est parfois bien pratique de donner un nom aux threads, quand ils

New Comments to this post are disabled
 
Page view tracker