SCORM 跨域、SCO-Fetcher 或任何其他解决方案
为了找到解决方案，我们在美国各地都有 LMS 服务器和内容服务器，因此用户可以从最近的位置获取内容。
我遇到了一个使用 SCO-Fetcher 的解决方案，在下面的两个链接中提到并在下面进行了说明，但我找不到有关如何实施类似解决方案的任何信息。
此处：http://elearningrandomwalk.blogspot.com/2006/08/sco-fetcher .html
如果有人对此有任何想法或信息，我们将不胜感激。
Trying to find a solution to this, we have our LMS Server, and content servers all across the US, so the user gets their content from the closest location.
I've come across a solution using SCO-Fetcher, mentioned in these two links below and illustrated below, but I cannot find any information on how to implement a similar solution.
here: http://elearningrandomwalk.blogspot.com/2006/08/sco-fetcher.html
If anyone has any thoughts or information regarding this, it would be most appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我为一家内容提供商工作，他们必须与许多不同的 LMS 进行交互，而跨域一直是一个痛苦的问题。
尽管如此，SCORM 并不真正适合跨域。我在跨域方面的经验违反了 AICC 标准。过去我们使用签名的java小程序来执行跨域通信，但目前我们使用一些隐藏的 flash* 我们通过 JavaScript 进行交互的 SWF 文件。这要求 LMS 在其 Web 服务器上安装 crossdomain.xml 文件以允许通信，但我们的一些客户对此犹豫不决。
* 我们的产品已经大量使用闪存，因此这对我们来说并不是一个繁重的要求。
我们现在正在认真考虑的解决方案是“Content Server 上的运行时服务”的变体，如 跨域脚本文档。
内容服务器将运行课件本身，就像它是一个学习管理系统一样，并将所有 API 调用代理到真正的学习管理系统。下图显示了通信路径：
此外，您的启动 URL 不会直接指向内容 (例如，
http://abc.com/content/sco.html），但到内容服务器上的软件应用程序（例如，http://abc.com/access.php?content=sco.html&permissions=OAUTH_ID)，然后它将像 LMS 本身一样提供内容。另外，刚刚看到关于跨域的这篇文章域通信虽然不是 SCORM 特有的，但可能会提供一些替代的实现思路。
I work for a content provider who has had to interface with a lot of different LMSs and cross-domain has always been a painful issue.
The document you linked to not-withstanding, SCORM doesn't really cater for cross-domain at all. My experiences with cross-domain has been against the AICC standard. In the past we've used a signed java applet to perform the cross-domain communications, but currently we are using a little hidden flash* SWF file which we talk to via javascript. This requires the LMS to have a crossdomain.xml file installed on their web server to allow the communication, which some of our customers balk at.
* Our product heavily uses flash already, so this was not an onerous requirement for us.
The solution that we are seriously considering now is a variation on the "Run-time service on Content Server" as suggested in section 4.8 of the cross-domain scripting document.
The content server would run the courseware itself, as if it were an LMS, and proxy all the API calls to the real LMS. The diagram below shows the communication paths:
Also, your launch URL wouldn't be directly to the content (e.g.,
http://abc.com/content/sco.html) but to the software application on the content server (e.g.,http://abc.com/access.php?content=sco.html&permissions=OAUTH_ID), which would then serve the content as if it was an LMS itself.Also, just came across this article on cross-domain communication which, while not SCORM specific, might provide some alternative ideas for implementation.
我知道这是一个老问题，但我想我会分享：几年前我也遇到过类似的情况，并决定使用 iframe hack 绕过跨域限制。它所需要的只是一点 JavaScript 和 HTML。它适用于较旧的浏览器，包括 IE6。
Chuck，你最终使用了什么解决方案？
I know this is an old question, but thought I'd share: I had a similar situation a few years ago and settled on an iframe hack to get around the cross-domain restrictions. All it requires is a bit of JavaScript and HTML. It works on older browsers, including IE6.
Chuck, what solution did you wind up using?