I'm not confident the atmosphere wicket extension can handle caching and other necessary options for a real world app. It works great for simple demo's but we are having issues with pages that have lots of self updating components and occasional VPN issues. I'm looking for a road map for wicket support of a push API since the 0.5 atmosphere-wicket and atmosphere version 1.0.0 are not robust enough for our needs. Unless my understanding of the state of the wicket atmosphere extension is way off, it looks like I'm going to abandon the extension and fallback to a polling solution that works reliably. Also other disappointing limitations like atmosphere not being able to handle web.xml filter-mapping dispatcher options made the transition less than profitable.
-- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-6-Atmosphere-atmosphere-version-1-0-4-tp4654048p4654054.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
