Ok, thanks for this. The only problem that I can see is that I don't have the event context at the time I am constructing the URL. I will only have the context in my asynchronous push event.
I'll take a look at how tapestry adds the context to the URL in ComponentResources.createEventLink(String eventType, Object... context) and see if I can mimmic the behaviour in my asynchronous thread. Cheers, Lance. -- View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5699369.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
