Microsoft IE7 has a neat phishing filter that checks each URL against a list of known phishing sites. But this has turned out to be a problem when multiple frames are involved. In Microsoft's own words, "When you use Windows Internet Explorer 7 to visit a Web page, the computer may respond very slowly as the Phishing Filter evaluates Web page contents." Microsoft released a patch that minimizes the problem last week. The corresponding Knowledge Base article is titled "The computer may respond very slowly as the Phishing Filter evaluates Web page contents in Internet Explorer 7
", ID 928089 and has download links for the patch. http://support.microsoft.com/kb/928089
For some reason many people seem to be unaware that there is an IEEE standard that specifies an XML schema for the CMI data model used in SCORM. I put a detailed explanation of what this means, including a link to the schema file itself, at http://www.ostyn.com/standards/docs/xml1484-11-3.htm
Just ran across what looks like an "out of the box" solution for SCORM cross-server delivery. It is a recently released product called "WebDelegator" at www.webdelegator.com
. The price is reasonable ($99) and you can download a free 30 day trial without the hassles of preregistering. It runs on Windows platforms, even older versions, so it looks like it can be economically deployed using an existing box in a Windows shop. One of its features is the ability to forward outside the LAN. So, for example, lms.example.com could go to a LMS web server in a LAN, and content2.example.com could go to the web server of a content vendor outside the LAN. Basically all the LMS would have to to do is "munge" the launch URL for the SCORM resources to set the appropriate path. For example, if a resource href is www.contentprovider.com/something/something.htm
the actual URL the LMS passes to the client side of the SCORM RTE to launch a SCO could be contentprovider.example.com/something/something.com. A couple of caveats: I have not actually reviewed this product, only its published specs, and I cannot find a review of it online yet. Also, it appears that it may be limited to forwarding to specific IP addresses rather than the FQDNs for servers. The later one is not a showstopper, since the IP addresses of content servers are usually quite stable.