From: Charles on
Hi Mike

Thanks for the idea. I think I have it sorted now, but I will keep this in
mind.

Cheers

Charles


"Mike" <m.pires(a)netcabo.pt> wrote in message
news:Ox499s#XKHA.3428(a)TK2MSFTNGP06.phx.gbl...
> I don't know if is to late, to give you one idea,
>
> I did have the same problem, i did have to develop one small app, to keep
> a VPN tunnel up and running, until change one of the VPN pix,
>
> What i did do to kip the connection up and running was a ICMP app, using
> Background worker this basically ping a host from the other lan and this
> way my pix that was broke dint let the tunnel get down.
> And the BackGroundWorker don't let my CPU get stress up.
>
> Cheers,
>
> Mike
>
>
> "Charles" <blank(a)nowhere.com> wrote in message
> news:eG3x2DvWKHA.4780(a)TK2MSFTNGP05.phx.gbl...
>> This is a follow up to an earlier post, about a Threading.Timer that
>> occasionally fired at odd times. In that case I discovered that low
>> memory meant that the machine 'froze' intermittently and a timer callback
>> could fire after 30 seconds instead of every 10 seconds as intended.
>>
>> I now find that if the machine becomes preoccupied with another task, I
>> get the same effect. This is a very bad state of affairs, as I can no
>> longer rely on my 10 second tick occurring every 10 seconds.
>>
>> I need to have a reliable 10 second timer, such that an event happens
>> every 10 seconds. It's no good if I get two events after 20 seconds, I
>> need one every 10 seconds.
>>
>> How is this possible to guarantee in .NET? The app is running on Windows
>> Server 2003 x64.
>>
>> TIA
>>
>> Charles
>>
>>
>