The reason is that "other" browsers use a media player component that
reconnects to the server. The "session" is linked to the browser
instance. As a result, the session is lost when the mediaplayer connects
to get the audio data.
Whap happens in "other" browsers is the equivalent of storing a
bookmark, closing the browser, starting a new browser and retrieving the
bookmark. This will not work in your application because you depend on
the session to remain the same.
The solution is to either NOT depend on the session for the audio data
retrieval, OR to include the session ID in the url itself. Which
solution you choose and how you wish to implement that solution is
entirely up to you. We'll be glad to help you regardless oft he
implementation you pick. Just don't expect your application to function
without modification, it is not Tomcat's nor the browser's "fault" that
it does not work, it is something you need to address in your web
application.
M.
But if I change to use IE6/IE7/IE8, this problem never happened.
Does someone know the reason? thanks.
This message and attachment(s) are intended solely for use by the addressee and
may contain information that is privileged, confidential or otherwise exempt
from disclosure under applicable law.
If you are not the intended recipient or agent thereof responsible for
delivering this message to the intended recipient, you are hereby notified that
any dissemination, distribution or copying of this communication is strictly
prohibited.
If you have received this communication in error, please notify the sender
immediately by telephone and with a 'reply' message.
Thank you for your co-operation.
