Yes,I believe if we use the tapestry's existing event processing chain,we will get the rendered html we want. The question is:in the back of tapestry's existing event processing chain,tapestry use PageRenderQueue(or something else) and RenderCommand to render blocks/zones/components. So , why don't we just use PageRenderQueue(or something else) and RenderCommand ? it looks more natural.
Thank you for your guidance,now I have got more clearly on tapestry's architecture. -- View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5709684.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
