StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POUsing a callback instead of returning state object
primarykey
Id
2205959
data
AcceptedAnswerId
2206176
AnswerCount
4
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-02-05T08:47:41.567
FavoriteCount
0
LastActivityDate
2010-02-05T10:23:44.963
LastEditDate
2010-02-05T08:49:34.823
LastEditorUserId
40581
OwnerUserId
40581
ParentId
0
PostTypeId
1
Score
1
ViewCount
1331
LastEditorDisplayName
text
Body
In my application, I'm executing a transaction which can be in three different states at the end of the execution: <ul> <li>Success</li> <li>Failure</li> <li>Pending</li> </ul> Depending on the state, the application client will want to perform different actions. In the case of success, they will want to retrieve the transaction result (a Widget). In the case of failure, they will want to receive the error reason. In the case that the transaction is pending, they will want to schedule a time to retry. Currently I return an object with the following methods: <pre><code>public interface Result() { State getState(); Widget getWidget(); // Success Reason getFailureReason(); // Failure Callable<Result> getTask(); // Pending } </code></pre> The idea is that the client checks the state of the result object, and invokes the appropriate method depending on it's value, e.g. <pre><code>if (result.getState() == State.PENDING) { result.getTask(); } </code></pre> I was thinking that it might be preferable to use a callback instead, e.g. <pre><code>public interface TransactionCallback() { void onFailure(Reason reason); void onSuccess(Widget widget); Delay onPending(Delay previous); } </code></pre> Where <code>Delay</code> is a class representing a <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/TimeUnit.html" rel="nofollow noreferrer">TimeUnit</a> and period, allowing the application to reschedule the transaction execution. Another alternative is to throw an exception wrapping the failure reason (as it should only fail in exceptional conditions), and keep the <code>onSuccess</code> and <code>onPending</code> methods. So my question to SO is this: is the use of a callback an appropriate pattern for this particular problem, or can anyone suggest something more appropriate?
Tags
<java><callback><design-patterns><listener>
Title
Using a callback instead of returning state object
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USDavid Grant
UserOwnerUserId
1. USDavid Grant
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POUsing a callback instead of returning state object
 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.