Ensure that we don't allow clients to provide duplicate signals in cursors #1312

DamianEdwards opened this Issue Jan 12, 2013 · 2 comments


None yet

3 participants


Currently, if you manipulate the URL of a reconnect to make the cursor contain duplicate entries for a single event key, the connection can be subscribed multiple times to the same event key. Even if this isn't the case (for some reason) the cursor returned from the server continues to contain the duplicates, so something is holding on to the double cursor reference.

@halter73 halter73 was assigned Jan 14, 2013


@Xiaohongt Xiaohongt closed this Jan 15, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment