Hi Gerd,
firstly, thank you for sharing the work you have done so far! - we are aware that the SCORM module is not great on performance in certain areas, and Piers and I hope to improve it a lot. At the moment we are focusing on bugs in the tracker that cause loss of functionality, and will look at the performance and feature requests later on down the track.
The File API for Moodle 2.0 is changing a lot, and the use of file.php will also be quite different - see here for more details:
http://docs.moodle.org/en/Development:File_APIWe won't be looking at putting in a new file handler just for the SCORM objects at this stage.
there's a lot in the document you uploaded, but I'd like to pull out a couple of things....
5.1 Issue 1 - I haven't seen an SCO with a simple html file take 60 secs to load - this sounds a bit strange! - have you got a Sample scorm object that you could provide that would demonstrate this for us? - the resolution you suggest (using a new file handler for SCORM) isn't something we would implement at this stage - especially with the changes happening with the file api in Moodle 2.0 however your breakdown of "How SCORM content is currently played in Moodle" is useful, and there is work that can be done in those steps to improve performance!
6.4.2 - you mention a SCORM object that does not load? - is it possible that you might be able to share this with Piers and myself to allow us to do some testing? - even better, if you had some reference SCORM objects you would be willing to share, please make them available via the SCORM Repository here:
http://moodle.org/mod/data/view.php?d=50also just in case you weren't already aware - the
Moodle Tracker is where we store all the bug reports/feature requests for Moodle - the SCORM ones can be seen here:
http://tracker.moodle.org/browse/MDL/component/1008in 6.4.1 of your report you mention that you upgraded to build 20080711 to fix some of the bugs related to display in the scorm module - at this date those bugs had only been fixed in the HEAD branch of
CVS or Moodle 2.0 - Those fixes only went into 1.9Stable a couple of days ago.
once again, thanks for the detailed report! - if you have any other performance related fixes for code it would be great to see them in the Moodle Tracker!
thanks,

Dan