>  I like the idea of the AjaxPushBehavior mentioned in the issue tracker
> posting.  At one point I tried extending AbstractDefaultAjaxBehavior, and
> adding an addOnLoadModifier() which asynchrously called back on page load
> and then I blocked that thread, with the intention of waking up that thread
> and calling AjaxRequestTarget.addComponent when some action took place on
> the server.  The problem that I had was that it seemed like all other
> requests for that session were also blocked even ones that had nothing to do
> with that behavior.

You would have to make sure the request for a push behavior is handled
by it's own IRequestTarget, which then would return null at the
getLock method. That would prevent the request being synchronized on
the whole session. This also means you have to take care about the
reentrant behavior of that push behavior.


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
Wicket-user mailing list

Reply via email to