Did not complete in time for 1.7DR3 cutoff.

Note that the fix for this bug is central to the Ajax Push implementation. In some cases, the ThreadLocal variable for PersistentFacesState had a spurious value (likely from the previous thread invocation). When a server-initiated render was requested with one of these threads, PersistentFacesState.getCurrentInstance() in application code could return the PersistentFacesState associated with the thread, not the PersistentFacesState invoking the render. This would result in later renders being directed to a wrong or nonexistent browser window. The fix is to call PersistentFacesState.setCurrentInstance() prior to execute() and render() in PersistentFacesState.

Note that the presence of spurious values may indicate that we are not calling release() when we should be. Missing release() calls result in stale PersistentFacesState being left as ThreadLocal values.

after reloading the application on the iPod:
can't parse stream for /index.jsp
at D2DViewHandler.renderResponse line 525

A round of testing was requested from the development team. Responses as follows:

We need to fix the layout shift that occurs to the participants and chat area when the slide refreshes (FF2.0).

preload the next x slides so they wouldn't load in front of the viewers

slides did not update on iPod

exception on iPod:

failed to append element[tag: html, attributes: ] into #document
at DOMResponseWriter.appendToCursor line 470