StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16203893
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-04-24T23:22:07.767
FavoriteCount
0
LastActivityDate
2013-04-24T23:29:55.463
LastEditDate
2013-04-24T23:29:55.463
LastEditorUserId
2293350
OwnerUserId
2293350
ParentId
16196172
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<h2>Generic Solution</h2> <p>As you are using a Comet server, make the client flag as "seen" each event it receives.</p> <h2>Problem</h2> <p>If each client needs to respond to each notification, the traffic to your server may increase significantly. So, your server performance and network might get affected.</p> <p>Other things, as event ordering might be considered for your solution.</p> <h2>Solving the problem</h2> <p>The solution you have to adopt will depend on how critical is for your application the awareness of such events. If the client is able to work as expected even missing some of those events, consider a more relaxed solution.</p> <ol> <li>Answer each event instantly</li> </ol> <p>Whenever you receive an event from the server, ask server to flag it as "seen". If the server has events sent and not flagged as seen, make sure to resend them to the client. Becareful not to process the same event more than one time (on client-side) due to network latency (when your server sends the same event a second time before receiving the acknoledgement the first has arrived).</p> <ol> <li>Relaxed approach</li> </ol> <p>When your client receives an event, storage it as the "last event received". Whenever your client reconnects, ask server to send again those missed events since the last you have stored. If you lose track of which one was the "last event received", make sure your server retransmission starts from a point which will make sense for your client</p> <hr> <p>These ideas might be implemented using a queue on the Comet server, but be sure to implement it correctly. If the order of those events are important, you must assure it on your implementation. Be sure not to create giant queues or indefinetly many of them. Consider other aspects too.</p> <p>Hope I helped.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to avoid missing web push notifications while connecting to comet server
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USWalter Macambira
UserOwnerUserId
1. USWalter Macambira
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. 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.