StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14058697
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-12-27T17:29:22.073
FavoriteCount
0
LastActivityDate
2012-12-27T17:38:21.403
LastEditDate
2012-12-27T17:38:21.403
LastEditorUserId
1932601
OwnerUserId
1932601
ParentId
14058373
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
When you deal with a typical "flow" of processing, possibly even multithreaded/concurrent processing flow the best approach to take is "mailslots"/message pumps. By exchaging messages you can easily coordinate multiple layers of your application and that includes reporting errors, notifying the next chain of command etc.. I do not mean Windows messages, I mean something like: <pre><code>public abstract class Message { public abstract void Process(); } </code></pre> Then: <pre><code>public class MessageQueue { private Queue m_Queue; public void Post(Message msg) {....} public void Process() {.....} } </code></pre> Then you allocate a MessageQueue on every thread/processing tier of your app and pass messages like so: <pre><code> GUIMessageQueue.Post( new ErrorMessage("Internal async file reader ran out of buffer")); </code></pre> On GUI thread put a timer that read GUI queue and calls it's Process(). Now you can create many Message-derived work items to execute various tasks that very easily orchestrate between threads/logical tiers. Also, messages may contain references for datapieces that they relate to: public AirplaneLandedMessage: Message { public Airplane Plane ...... } Here is some real code that I use in massively parallel chain-processing system: <pre><code>/// <summary> /// Defines a base for items executable by WorkQueue /// </summary> public interface IWorkItem<TContext> where TContext : class { /// <summary> /// Invoked on an item to perform actual work. /// For example: repaint grid from changed data source, refresh file, send email etc... /// </summary> void PerformWork(TContext context); /// <summary> /// Invoked after successfull work execution - when no exception happened /// </summary> void WorkSucceeded(); /// <summary> /// Invoked when either work execution or work success method threw an exception and did not succeed /// </summary> /// <param name="workPerformed">When true indicates that PerformWork() worked without exception but exception happened later</param> void WorkFailed(bool workPerformed, Exception error); } /// <summary> /// Defines contract for work queue that work items can be posted to /// </summary> public interface IWorkQueue<TContext> where TContext : class { /// <summary> /// Posts work item into the queue in natural queue order (at the end of the queue) /// </summary> void PostItem(IWorkItem<TContext> work); long ProcessedSuccessCount{get;} long ProcessedFailureCount{get;} TContext Context { get; } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to pass status information to the GUI in a loosely coupled application
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USitadapter DKh
UserOwnerUserId
1. USitadapter DKh
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to pass status information to the GUI in a loosely coupled application
 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. COHere is code that I use in massively parallel process-chain system:
 singulars
 PostPostId
 PO
 UserUserId
 USitadapter DKh

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.