Threads v Timers

[PRR]

Use a System.Timers.T imer. You can call a function on elapsed event.
In the service on start method, enable the timer.

Timer(MSDN):
"The Timer component is a server-based timer, which allows you to specify a recurring interval at which the Elapsed event is raised in your application. You can then handle this event to provide regular processing. For example, suppose you have a critical server that must be kept running 24 hours a day, 7 days a week. You could create a service that uses a Timer to periodically check the server and ensure that the system is up and running. If the system is not responding, the service could attempt to restart the server or notify an administrator."

[sanjib65]

Threads v Timers

I'd like to extend this interesting thread a little further. What is the basic difference between Timer and Thread. Both are used to pause the application for a certain time, I guess?

[PRR]

Thread and Timers are different.Timer s are used to execute certain tasks after a defined interval. Threading is execution of tasks simultaneously. Some timers internally use threads( System.Timers.T imer for eg).
Thread: Programs that use more than one thread properly/ correctly are better responsive and more use friendly. Having multiple threads in a program, enables the program to do more work simultaneously. Multiple threads can exists within same process sharing memory, files and other resources.

Timers: Timer objects in .Net Framework allow you to execute certain function/code regularly. There are three timers in Framework
1. System.Timers.T imer
2. System.Windows. Forms.Timer
3. System.Threadin g.Timer

Each application has a pool of threads, normally around 20-50 called threadpool. Threadpool are background threads. System.Timers.T imer in its elapsed event spawns new threads( from threadpool).

[sanjib65]

Many thanks PRR, nicely explained but I wanted to know another thing. Suppose, in an data application using AJAX when we use System.Thresdin g.Thread.Sleep( 3000) and pause the UpdateProgress for 3 seconds, does it not do something(suppo se updating data in a ListView) after a certain interval? I mean, it seems doing something like Timer though both are different in nature, no doubt.
Best of Luck.

[tlhintoq]

Sanjib65: In the future please do not hijack someone else's thread/question for your own needs. You are always welcome to start a new thread and even reference an existing thread.

"I was looking at this question xxxxxxxx when it got me thinking about zzzzzzz"

I have split your question and PRR's answers to their own thread.

[tlhintoq]

System.Thresdin g.Thread.Sleep( 3000) and pause the UpdateProgress for 3 seconds, does it not do something(suppo se updating data in a ListView) after a certain interval?

When the thread is asleep - NOTHING happens on that thread. Loops are not run, events are not reacted to, queue's are not processed. NOTHING.

My personal opinion and coding style:
Thread.Sleep is rarely what someone really wants, but it often what people will use. In your example of wanting to pause the update of a progress bar. If the progress bar is on it's own thread, and nothing else happens then it might be ok. But if you sleep the progressbar, and it is supposed to react to an event on another thread so it can update, then it won't hear the event it is supposed to react to. I personally prefer a loop that will cause it to continue to be responsive, yet not proceed in code.

DateTime dtBailout = DateTime.Now.AddSeconds(3);
while (DateTime.Now < dtBailout)
{
    Application.DoEvents();
}
// Continue doing something

[sanjib65]

tlhintoc, as a moderator you can always overpower me and delete my thread and even you can write this kind of line:

Sanjib65: In the future please do not hijack someone else's thread/question for your own needs.

But I have a question, is your forum not open for other good free tutorials or links? If someone like me wants to share his nice experience of learning elesewhere and give a reference to that link, it will be deleted immidiately?
Then what is basic of sharing knowledge in a FORUM?
If my tone seems to be harsh please forgive me. If this is the rule here, I am bound to obey and in future I won't refer any free link where one can get his helps.
Best of Luck

[tlhintoq]

The forum is available to all, provided they follow the posting guidelines, which are quite fair.

Threads and posts are free. There is no reason to ride someone else's coat tails when you can just as easily ask your own question.

Your post did not try to resolve the original poster's question. It diverted the attention AWAY from what was asked and onto your need. It was was not deleted - It was made into it's own thread so it would get the same attention and respect.

[sanjib65]

You did not answer my main question:

But I have a question, is your forum not open for other good free tutorials or links? If someone like me wants to share his nice experience of learning elesewhere and give a reference to that link, it will be deleted immidiately?
Then what is basic of sharing knowledge in a FORUM?

Recently someone asked to know about making connections with MS Access Database. In response I posted this following link:

http://www.homeandlearn.co.uk/csharp/csharp_s12p4.html

You deleted the whole thread and instead posted two links of Bytes Tutorials on Database. Bytes tutorials are very good. I have gone through them, but is it mandatory here to read only these tutorials?
In forum guidelines I did not find any such dictum.

Best of Kuck

[tlhintoq]

Its rather up to the expert/moderator.

When a newbie posts a message whose sole content is to direct people to another site and thus away from this one, it looks like the new account was created just to steal traffic from this site.

When someone builds a history of posts that genuinely help others, and now and then that help comes from existing tutorials on other sites, then it is a reasonable post.