Course published as AICC will quit reporting status after connection failure.

Just checking you saw there was a screen shot on the code problem on the fist message.

I believe the reason we had the problem with the 4 clients in a small window is because they are located on an island just north of south America so maybe not the most stable internet connection back to America.   This would explain why one of the AICC bookmark api calls might timeout or fail.  After just a single failure it will not try to communicate with the server because "waitingAiccResponse" it true from that point forward since there is no code to reset it on failure.

This behavior would apply to any course and any platform because with AICC the course communicates directly with the server and the bug is inside AICCComm.html

I patched the course with the code posted above to handle "objXMLHTTP.onerror" and could not reproduce the problem anymore.

I'll see if i can try to generate you a log some time soon but i'm also very behind after loosing most of yesterday tracking this down and verifying.

To duplicate with any AICC course.

1. Launch and go to the second slide.  Clicking between the two slide will cause a bookmark request.

2. Disconnect wifi or unplug network from computer and click to the other slide.  You should see the http request fail in chrome console.

3. Turn wifi back on or plug network in.

4. You will not get another bookmark on slide change till exit which seems to set waitingAiccResponse back to false and starts to flush the queue.  In our case they either clicked the chrome X which sent nothing on exit or we only got the first few events from the queue but not any of the latter ones.

The main problem is that it quits sending in progress in the middle of the course which makes the exit behavior irrelevant.