StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8374382
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-04T09:21:49.837
FavoriteCount
0
LastActivityDate
2011-12-04T09:35:28.880
LastEditDate
2011-12-04T09:35:28.880
LastEditorUserId
225728
OwnerUserId
225728
ParentId
8374170
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
From an architecture point of view: Message Queues decouple bits of your application. You can in Windows Forms applications rely on the Message Queue that Windows creates and manages for you. Google for PostMessage/GetMessage etc. This is generally called "message passing". Typical Arcitecture <ul> <li>One part of your app "pushes" a request into a queue</li> <li>Some other part of your app "pulls" a request from a queue and writes a result to a second queue.</li> <li>The first part can then "pull" requests from the second "results" queue and display to a user.</li> </ul> So it looks like this: App --> REQUESTS QUEUE --> processing engine --> RESULTS QUEUE --> App The processing engine could be in the same app, on the same thread or in a different thread/process (or even different machine). You can use simple queues : say a <code>Queue<string>()</code> (as long as you use locks to access it) or increase complexity or more and more complex/functional queues. Issues with the naive strategy and other solutions ... things to think about: <ol> <li>What happens if you make a new request while the old one has not yet completed? </li> <li>What happens if an error occurs? Do you want errors inline? You can use another queue for errors?</li> <li>Do you want retries?</li> <li>What happens if a message is lost? (i.e. a request was pushed, but no response comes in...)? There are transactional queues etc.</li> </ol> Sample Code <pre><code> object oLock = new object(); Queue<string> requests = new Queue<string>(); Queue<string> responses = new Queue<string>(); Thread mThread; AutoResetEvent mEvent = new AutoResetEvent(false); public Form1() { InitializeComponent(); mThread = new Thread(ProcessingEngine); mThread.IsBackground = true; mThread.Start(); } private void ProcessingEngine() { string result; string request = null; while (true) { try { mEvent.WaitOne(); lock (oLock) { request = requests.Dequeue(); } var wc = new WebClient(); result = wc.DownloadString(request); lock (oLock) { responses.Enqueue(result); } } catch (Exception ex) { lock (oLock) { responses.Enqueue(ex.ToString()); } } } } private void timer1_Tick(object sender, EventArgs e) { lock (oLock) { //Stick in a new request requests.Enqueue("http://yahoo.com"); //Allow thread to start work mEvent.Set(); //Check if a response has arrived if (responses.Any()) { var result = responses.Dequeue(); listBox1.Items.Add(result.Substring(1,200)); } } } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POApp for monitoring changes
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USGrynn
UserOwnerUserId
1. USGrynn
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POApp for monitoring changes
 singulars
 PostTypePostTypeId
 PTQuestion
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.