Hi Folks, iam using Wicket 6.2.0 with Wicket-Atmosphere 0.4 and everything works great, but Iam not able to debug the websocket-transfer in Chrome Debug-Tools like its explained and working here : http://blog.kaazing.com/2012/05/09/inspecting-websocket-traffic-with-chrome-developer-tools/
Is there something wrong with the initialization of the WebSocket in Atmosphere so Chrome cant "identify" it as a WebSocket? Iam also want to know, how i could disable the window.info/.console output on every WebSocket-"Pull" Thanks in Advance for any Hints or Help :) - Matty -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/What-is-Atmosphere-doing-wrong-so-i-cant-debug-the-websocket-tp4654322.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
