Home/ Questions/Q 3809224
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T15:16:19+00:00

I’m writing a small application, composed by a gui and a couple of buttons.

  • 0

I’m writing a small application, composed by a gui and a couple of buttons. When the user clicks one of them, the program must download a webpage, do a couple of matching and return a value to the gui.
The question is, I must start a new thread every time the user clicks on that button, or there’s an alternative to threads for those kind of small tasks ( mainly, download contents from the web)?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You always have to use a different threads. Now how you use those different threads can be up to you. Look at the producer/consumer method where there is just an idle thread sitting in the background waiting for work to be queued. This seems to fit your job well. You should also use SwingWorker when possible because it helps with a lot GUI updates and refreshes. Finally, look at the java.concurrency package as it is very useful. Now days, I don’t think there is any reason to start a Thread manually without using some library that does all the locking and threading for you.

    • 0