Home/ Questions/Q 6818195
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T21:08:54+00:00

I need a better design for sleeping Task than Thread.Sleep, I’m using the Task

  • 0

I need a better design for sleeping Task than Thread.Sleep, I’m using the Task class.

In my wpf app i run a Task, this task runs another couple of tasks, each of this tasks first login to and Internet website, after they login they need to wait couple of seconds and inform the user when they will proceed further and this is my problem, because with Thread.Sleep i can’t report the progress.

There are more functions than login, it’s about 5-6, all of them request an Internet resource, and between them there need to be a sleep time with remaining time report send do gui, this 5-6 function are all in one Task, but there could be many tasks.

What i need is to make the task wait, but also allow it to send updates on the remaining time to proceed to the GUI.

Do you have any ideas for this problem, how to make it better, maybe you have some design patterns already for such problem?

I have heard also that using Thread.Sleep is a poor design practice.

EDIT: No one knows ?
Whats with some kind of self contained timer with thread wait like waithandle, autoresetevent, anybody?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Forget using Thread.Sleep. Instead, run your task in a background thread and use a WaitHandle with an AutoResetEvent. (Links: WaitHandle/WaitOne / AutoReset)

    Your background thread can send updates to UI with async delegates, but the calling thread will wait it until either thing happens:

    1) Your thread reports it has completed its task by using yourwaithandle.Set();

    or

    2) the waiting thread timeouts (timeout value is set as parameter to WaitOne() -method).

    • 0