StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7674918
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-10-06T13:29:08.553
FavoriteCount
0
LastActivityDate
2011-10-06T13:29:08.553
LastEditDate
LastEditorUserId
0
OwnerUserId
1738
ParentId
7671932
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I don't think you'll be able to do this, as I don't think this sort of thing is what the callback mechanism was designed for. I can see what you're trying to achieve, and I can see how you've arrived at this question, but I think as long as your client uses the cache-aside pattern everywhere you're touching the cache you'll get the effect. For review, the cache-aside pattern is: <ul> <li>Check the cache for the desired item </li> <li>If the item is NOT in the cache <ul> <li>Get the item (from whatever source e.g. database, web service) </li> <li>And put it into the cache </li> <li>Return the item to the caller </li> </ul></li> <li>If the item IS in the cache <ul> <li>(Cast it to the expected type) </li> <li>Return the item to the caller</li> </ul></li> </ul> e.g. <pre><code>Order order; // Check to see if the order is in the cache Object cachedOrder = m_cache.Get(OrderId.Text); if (cachedOrder == null) { // The order is NOT in the cache, so get it from the web service order = OrderWebservice.Get(OrderId.Text); // Cache the order for 10 seconds m_cache.Add(OrderId.Text, order, New TimeSpan(0,0,10); } else { // The order IS in the cache, so cast it order = (Order)cachedOrder; } // Return the order to the client, whether it's the cached order or the one from the web service return order; </code></pre> In this way, the cached order will never be more than ten seconds old, because if it times out of the cache, the next caller will get a null result from the cache and call the web service again to get the order from the web service. You'll get the same effect, but as the cache will be filled on demand you should see a lower impact on your server as it won't be spinning up a web service request every ten seconds.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAppFabric Notification on timeout
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPhilPursglove
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. This table or related slice is empty.
CommentsPostId
1. COThank you for your answer. The 10 sec was for the example. In real it's more and the call to the webservice to fill the cache is very heavy (10sec) so I cannot wait to have a customer to call the page in order to cache the result of the webservice.
 singulars
 PostPostId
 PO
 UserUserId
 USfabrice

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.