I recently run into a problem that has make me consider whether continuing using Wicket or not for a project. I hope guys you can throw some light into it.
I need to create a web application that uses ajax to keep itself udpated while still allows the user interact with it also using Ajax. Imagine something as GMail, Documents, Facebook, Twitter, etc. On this pages, is very common to have some ajax COMMET, long polling or also known as inverse AJAX to keep the page updated. But that doesn't prevent the user to click here and there and update the page also using AJAX. They are independent XMLHttpRequest with a browser can handle perfectly. I was thinking about doing this on Wicket, but apparently it's impossible by design: https://issues.apache.org/jira/browse/WICKET-2437 Page objects aren't thread-safe and wicket will block any other thread (AJAX call) that tries to access the page while another request (for instance our long poll) is there. Have you ever find yourself into this kind of problem? What's the workaround if any? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
