-
March 1st, 2010, 09:17 AM
#1
The unique ID of the subscription request is not related with the user.
Requests from multiple users for the same item only cause one subscription request to be issued to the Remote Data Adapter, as you would expect.
Hence, at any time, there is at most one subscription in place for each item.
However, depending on the user activity, it is possible that an item is subscribed to and unsubscribed from for multiple times in sequence.
In order to distinguish these subscription instances, we introduced this unique ID.
Hence, the ID is redundant (the item name would be enough), but if you managed subsequent subscription requests for the same item through independent threads,
the ID would be helpful in avoiding conflicts between these threads without the need of a careful synchronization between them.
Similar Threads
-
By kclerc in forum Adapter SDKs
Replies: 7
Last Post: April 12th, 2010, 11:40 AM
-
By k.mcc2009 in forum Adapter SDKs
Replies: 1
Last Post: May 21st, 2009, 09:41 AM
-
By jsharpe in forum Client SDKs
Replies: 4
Last Post: February 4th, 2009, 11:45 PM
-
By jsharpe in forum Adapter SDKs
Replies: 0
Last Post: January 10th, 2007, 04:03 PM
-
By jsharpe in forum Adapter SDKs
Replies: 3
Last Post: September 28th, 2006, 02:03 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 11:29 AM.
Bookmarks