On Fri, 27 Aug 2010 08:45:06 -0300, Dmitry Gusev <dmitry.gu...@gmail.com>
wrote:
FYI
http://dmitrygusev.blogspot.com/2010/08/gae-and-background-workers-in-tapestry5.html
Hi! Nice post!
Two comments:
* "In Tapestry5 every page should have a template file with markup". This
is not correct. If your page doesn't have a template and doesn't generate
any response at all, an exception will be thrown. If your page returns a
StreamResponse in its onActivate() method, no exception is thrown.
* "The problem here is that Tapestry5 also uses Filter API to handle
requests and usually declared to serve all incoming requests:" Tapestry is
implemented as a servlet filter, so it doesn't necessarily serves (i.e.
generates a response) for every request. Specifically in GAE, which could
start a new application instance for a request if no request was made
recently, your LazyTapestryFilter is an improvement. In normal conditions,
just the contribution to the IgnoredPathsFilter is the only needed step.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
