About stoping threads with lengthy operations

Question

0.00/5 (No votes)

See more:

Hello guys!

I have a program that uses some threads at the same time that retrieve a page, wait for response, parse the response and then save the data in a DB using Sqlite.

Now when i want to close my program and there are these threads running it takes some time so it closes. how can i abort the page retrieval or the DB update/insert when i need to close my program, quickly?

Posted 14-Jul-11 5:51am

manchukuo

Updated 14-Jul-11 7:02am

thatraja

v3

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

#realJSOP · Answer 1 · 2011-07-14T06:04:00

Solution 1

Use the asynchronous reader execute methods (BeginExecuteReader/EndExecuteReader instead of ExecuteReader, for instance).

Posted 14-Jul-11 6:04am

#realJSOP

Comments

manchukuo 14-Jul-11 12:19pm

oh i forgot i am using sqllite

Philippe Mori · Answer 2 · 2011-07-16T10:55:00

I would say hide the form until the operation is completed and then close it. This would be adequate if the wait is at most a few seconds and then intend is to make it appears responsive...

BackgroundWorker can also be used and cancelled... Assuming that you can check for cancellation often enought, then the background task would be cancelled soon.

If you have a single long operation, then you might consider splitting that operation into multiple ones...