I see... I might keep going with the DWR approach then. So If I understand your proposal.
1. Use the incoming page request (& component resources) to generate a URL. Should this URL be to "activate" to component or to do the actual work (eg "doPush" in my example)? 2. In the asynchronous event (non web thread), I construct a fake request with the URL and spoof it into the RequestGlobals. I'm still not entirely sure how I would fire the "doPush" event from here (passing it a context) and get the resultant block back. Is there a service in the registry I should be calling? Thanks, Lance. -- View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5697808.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
