forked from cawerkenthin/cmi5-AU-Simulator
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple Completed and Passed statements could be sent for one registration #11
Comments
This can be resolved by the same local storage mechanism in issue #8 |
It should handle users that logged in using different devices too. However I can see that this might be out of scope. |
The AU also has the option to use the State API, which would be a better place than local storage for that situation.
…________________________________
From: Thomas Turrell-Croft ***@***.***>
Sent: Friday, July 9, 2021 10:59 AM
To: adlnet/cmi5-Client-Library ***@***.***>
Cc: Werkenthin Art ***@***.***>; Comment ***@***.***>
Subject: Re: [adlnet/cmi5-Client-Library] Multiple Completed and Passed statements could be sent for one registration (#11)
It should handle users that logged in using different devices too. However I can see that this might be out of scope.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA6XH36YNJKC3NB2VH6JLS3TW4MGLANCNFSM5ACTFKHA>.
|
Agreed that State API is better place to store data that may need to be shared across devices. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I believe that the cmi5 spec requires that only one Completed and or Passed statement is sent by the AU.
The AU could use the agent xAPI state resource to store if it has previously sent Completed or Passed statements. I don't believe the AU should attempt to check the existence of the Statements in the LRS because some LMS might prohibit an AU from requesting statements.
The text was updated successfully, but these errors were encountered: