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.