| 1441 |
ariadna |
1 |
=== 4.5 Onwards ===
|
|
|
2 |
|
|
|
3 |
This file has been replaced by UPGRADING.md. See MDL-81125 for further information.
|
|
|
4 |
|
|
|
5 |
===
|
| 1 |
efrain |
6 |
This files describes API changes in core_xapi libraries and APIs,
|
|
|
7 |
information provided here is intended especially for developers.
|
|
|
8 |
|
|
|
9 |
=== 4.3 ===
|
|
|
10 |
* The default state store will throw and exception if the activity ID is not
|
|
|
11 |
a numeric value. This is to avoid problems with the database when using
|
|
|
12 |
the default state store. If a plugin requires a non numeric activity ID,
|
|
|
13 |
it must implement its own state store.
|
|
|
14 |
* New xAPI state webservices:
|
|
|
15 |
- core_xapi_delete_states: delete all user state data for an activity
|
|
|
16 |
|
|
|
17 |
=== 4.2 ===
|
|
|
18 |
|
|
|
19 |
* A new state store has been introduced. Now plugins can store state data
|
|
|
20 |
by overriding the PLUGINNAME\xapi\handler::validate_state method.
|
|
|
21 |
* New core_xapi\state_store class to handle the state data storing. Plugins
|
|
|
22 |
can provide alternative state store implementations by overriding the
|
|
|
23 |
PLUGINNAME\xapi\handler::get_state_store method.
|
|
|
24 |
* New xAPI state webservices:
|
|
|
25 |
- core_xapi_post_state: store a user state data
|
|
|
26 |
- core_xapi_get_state: gets a user state data
|
|
|
27 |
- core_xapi_get_states: get the list of user states
|
|
|
28 |
- core_xapi_delete_state: delete a user state data
|