StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3110316
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-06-24T13:24:45.247
FavoriteCount
0
LastActivityDate
2010-06-24T13:24:45.247
LastEditDate
LastEditorUserId
0
OwnerUserId
123110
ParentId
3110154
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Threads are a very good thing, I think. But, working with them is very hard and needs a lot of knowledge and training. The main problem is when we want to access shared resources from two other threads which can cause undesirable effects. Consider classic example: you have a two threads which get some items from a shared list and after doing something they remove the item from the list. The thread method that is called periodically could look like this: <pre><code>void Thread() { if (list.Count > 0) { /// Do stuff list.RemoveAt(0); } }</code></pre> Remember that the threads, in theory, can switch at any line of your code that is not synchronized. So if the list contains only one item, one thread could pass the <code>list.Count</code> condition, just before <code>list.Remove</code> the threads switch and another thread passes the <code>list.Count</code> (list still contains one item). Now the first thread continues to <code>list.Remove</code> and after that second thread continues to <code>list.Remove</code>, but the last item already has been removed by the first thread, so the second one crashes. That's why it would have to be synchronized using <code>lock</code> statement, so that there can't be a situation where two threads are inside the <code>if</code> statement. So that is the reason why UI which is not synchronized must always run in a single thread and no other thread should interfere with UI. In previous versions of .NET if you wanted to update UI in another thread, you would have to synchronize using <code>Invoke</code> methods, but as it was hard enough to implement, new versions of .NET come with <code>BackgroundWorker</code> class which simplifies a thing by wrapping all the stuff and letting you do the asynchronous stuff in a <code>DoWork</code> event and updating UI in <code>ProgressChanged</code> event.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy is the explicit management of threads a bad thing?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USFrantišek Žiačik
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.