scorm 2004 中的终止请求
我正在开发一个 API 来处理 SCORM 2004，我想实现排序和导航算法。
在 SCORM 2004 手册中，他们写道： “终止进程从导航进程接收终止请求，并终止当前活动。根据终止请求的类型”
终止请求将保存在哪里？我如何读取终止函数中“终止请求”的值？
I am developing an API to handle SCORM 2004 , i want to implement the Sequencing and navigation algorithm .
in the SCORM 2004 handbook , they wrote :
"The termination process receives a termination request from the navigation process, and terminates the current activity. Depending on the type of termination request"
where is the termination request will be saved ? how i can read the value of the "termination request" in Terminate function ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
终止请求不一定会持续存在。将它们简单地视为传递到终止请求进程的参数。将哪个终止请求传递给终止请求进程由导航请求进程的返回值决定（您无法从终止函数中读取它们）。
您可以在《排序和导航》一书的第 4.5.1 节中找到可能的终止请求值的列表（我引用的是 SCORM 2004 第 4 版，位于 SN-4-27 页）。
您可能还想查看相互关联的排序伪代码算法的图表，可在 http://scorm.com/scorm-explained/scorm-resources/reference-poster/。
该“排序循环”是响应导航请求而执行的。导航请求可以通过两种方式之一触发。 SCO 通过运行时设置 adl.nav.request 值，或者用户单击 LMS 用户界面元素。
在 SCO 设置导航请求的情况下，一旦 SCO 调用终止，将调用总体排序过程。 SCO指定的导航请求将被传递到总体排序过程。
在用户通过 LMS 发起导航请求的情况下，LMS 将首先卸载 SCO（这应导致 SCO 调用终止），然后它将调用总体排序过程并向其传递用户选择的导航请求。
Termination requests aren't necessarily persisted. Think of them simply as a parameter that is passed into the Termination Request Process. Which termination request is passed to the Termination Request Process is determined by the return value of the Navigation Request Process (you can't read them from the Terminate function).
You can find a list of the possible termination request values in section 4.5.1 of the Sequencing and Navigation book (I'm referencing SCORM 2004 4th Edition, it's on page SN-4-27).
You might also want to look at the diagram of sequencing pseudocode algorithms relate to one another available at http://scorm.com/scorm-explained/scorm-resources/reference-poster/.
This "sequencing loop" is executed in response to a navigation request. A navigation request can be triggered in one of two ways. Either, the SCO sets an adl.nav.request value through the run-time or the user clicks on an LMS user interface element.
In the case of the SCO setting a nav request, the Overall Sequencing Process will be invoked once the SCO calls Terminate. The nav request that the SCO specified will be passed to the Overall Sequencing Process.
In the case of the user initiating a nav request through the LMS, the LMS will first unload the SCO (which should cause the SCO to call Terminate) and then it will invoke the Overall Sequencing Process and pass it the user selected navigation request.