Re: System.Threading.Timers

Microsoft's sscli 2 is using sleep functions.  See
http://dotnet.di.unipi.it/Content/sscli/docs/doxygen/clr/clr/win32threadpoo
l_8cpp-source.html.  ThreadpoolMgr::TimerThreadStart is the timer thread
entry point, note the call to SleepEx().
Also see Yun Jin's blog on System.Threading.Timer callbacks and his
comment on "sleeping", at
http://blogs.msdn.com/yunjin/archive/2005/05/08/415480.aspx with regard to
sscli 1

I don't have the time to track down the reference to Sleep[Ex] in sscli
1...


On Tue, 6 Jun 2006 09:56:05 -0500, Ivanoff, Alex <[email protected]>
wrote:

>Yes, waitable timers:
>
>http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/dllproc/bas
>e/waitable_timer_objects.asp
>
>
>-----Original Message-----
>From: Discussion relating to the specifics of the C# and Managed C++
>languages [mailto:[email protected]] On Behalf Of Peter
Ritchie
>Sent: Monday, June 05, 2006 23:42
>To: [email protected]
>Subject: Re: [DOTNET-CX] System.Threading.Timers
>
>NT waitable timer?  Your reference mentions waitable objects, I'll assume
>that's what you mean.  Waitable objects are used during initialization;
but,
>not to wait between periods or to raise the events...
>
>On Mon, 5 Jun 2006 23:07:00 -0500, Ivanoff, Alex <[email protected]>
>wrote:
>
>>I think you are wrong. System.Threading.Timer implemented using NT
>waitable
>>timer:
>>http://discuss.develop.com/archives/wa.exe?A2=ind0307A&L=DOTNET-
CLR&D=0&I=-
>3&P=1263
>>
>>
>>-----Original Message-----
>>From: Discussion relating to the specifics of the C# and Managed C++
>>languages [mailto:[email protected]] On Behalf Of Peter
>Ritchie
>>Sent: Monday, June 05, 2006 22:12
>>To: [email protected]
>>Subject: Re: [DOTNET-CX] System.Threading.Timers
>>
>>>Are we talking about System.Threading.Timer class?
>>Yes, that would be the class I keep mentioning...
>>
>>>With Change() methods?
>>The Change() methods just change the parameters used by the thread; I
>>mentioned the c'tors; but the Change() methods would apply.
>>
>>>This class internally uses private TimerBase class which is not much
>>>more than a bunch of MethodImplOptions.InternalCall methods.
>>Yes, those InternalCall methods go into the CLI and spawn the timer
>>background thread and manages dealing with the individual timers'
>>periods and duetimes.

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com