In addition to having the cron job (note, it's running on a compltely
different box , not the cron from GAE), I also use Dmitry's ping service to
watch the response times (http://ping-service.appspot.com). My cron job runs
about every three minutes , fetching all pages on the site and in 24hrs
cons
It seems to me that just getting the root index page would accomplish
most of the goal: keeping the whole application from being unloaded.
Your spider will do that, plus keep the page pool filled with pages.
Did you experiment with just getting the root index page?
On Sun, Jul 4, 2010 at 7:40 AM,
GAE doesn't do application unload, it shuts down entire appserver instance
whenever it wants no matter what application state is.
I believe the only reason why GAE do this is to balance GAE cluster
performance.
On Sun, Jul 4, 2010 at 22:31, Howard Lewis Ship wrote:
> It seems to me that just get
So if there was no page pool, the work I'm currently engaged in, then
there would be no advantage, in GAE, to pinging the application?
On Sun, Jul 4, 2010 at 11:55 AM, Dmitry Gusev wrote:
> GAE doesn't do application unload, it shuts down entire appserver instance
> whenever it wants no matter wh
On Sun, 04 Jul 2010 11:40:23 -0300, Alex Kotchnev
wrote:
My cron job runs
about every three minutes , fetching all pages on the site and in 24hrs
consumes about 20-30% of the free quota.
Just curious: why fetching all pages?
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestr
On Sun, 04 Jul 2010 15:31:32 -0300, Howard Lewis Ship
wrote:
It seems to me that just getting the root index page would accomplish
most of the goal: keeping the whole application from being unloaded.
Your spider will do that, plus keep the page pool filled with pages.
Did you experiment with
(Related to Tynamo's tapestry-security,
http://tynamo.org/tapestry-security+guide)
A custom exception handler added as an advice for the default one
wants to handle some specific type of exceptions and proceeds to call
PageResponseRenderer.render() in those cases. This works without
issues in T5.1
