Summary:
When making concurrent calls to LookupClient.QueryAsync it is possible to have query response data collisions. This issue was previously detailed out in a previous issue #209 . The changes made for #218 improve the likelihood of success, but they do not guarantee it.
Suggested fix:
I believe the correct solution to this problem would be to add a factory that does not allow duplicate active IDs. The factory would be in charge of tracking any "in use IDs" and therefore would have the information needed to always return a unique ID in relation to any currently in use IDs.
Summary:
When making concurrent calls to LookupClient.QueryAsync it is possible to have query response data collisions. This issue was previously detailed out in a previous issue #209 . The changes made for #218 improve the likelihood of success, but they do not guarantee it.
Suggested fix:
I believe the correct solution to this problem would be to add a factory that does not allow duplicate active IDs. The factory would be in charge of tracking any "in use IDs" and therefore would have the information needed to always return a unique ID in relation to any currently in use IDs.