TECHNOLOGIES
FORUMS
JOBS
BOOKS
EVENTS
INTERVIEWS
Live
MORE
LEARN
Training
CAREER
MEMBERS
VIDEOS
NEWS
BLOGS
Sign Up
Login
No unread comment.
View All Comments
No unread message.
View All Messages
No unread notification.
View All Notifications
Answers
Post
An Article
A Blog
A News
A Video
An EBook
An Interview Question
Ask Question
Forums
Monthly Leaders
Forum guidelines
Charly
NA
6
0
Brainstorming on correct data handling on application exit or error
Nov 19 2009 6:36 AM
Hallo all, I'm thinking about a good way to manage the execution ending of an application. The application gets data and processes for eacht row found an http request. If this fails I update a value in the db, status = 2 (error) else status = 1. Data that is fetched is updated by the stored procedure to status 9 (pending). So here I know exaclty the statues of my rows in the database when the process is done completely. Now I would like a way that when we quit the application, by ctrl-c catch or simple ":q" readline that the application quits only after the current running http request is not done (if there is one) and that this triggers an event that sets the status of this and all other data in the que back to status 0 (new). I could go the way of a thread and watches the status of a thead before doing my end event ? Any ideas ?
Reply
Answers (
3
)
web application development
ListView Problem