When & where to make 1st request for a Velocity generated page

[Eliot <tu...@juxti.com>]

Hi everybody,
After starting the servlet engine, the first request to use a Velocity
template normally takes a bit of time to generate the output, but then
once this initial request has been made, all subsequent requests to use
Velocity are quicker.

I don't want any users to experience this startup delay, so I thought
the most obvious thing to do would be to have a servlet with an init
method that makes a URLConnection to a page generated with Turbine's
Velocity service. Whenever the servlet engine is started, this init
method is called and the first request to a velocity generated page is
made by this servlet and not a user.

What I was hoping is if someone could tell me if this is a sensible way
of overcoming the 1st request delay for velocity/turbine, or if there's
a better way or a universally agreed method of doing this.

Thanks in advance & even more thanks for this fantastic framework,
Eliot

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: When & where to make 1st request for a Velocity generated page

[Eliot Sykes <in...@juxti.com>]

On Thu, 18 Apr 2002 13:52:48 -0400
"Eric Pugh" <ep...@upstate.com> wrote:
> What I am doing is use Canoo (a web test package) to walk through my
> pages tp get them cached..
> 
> Basically it takes an ant script that tells it how to reach each form
> or page..
> 
> It is a very slick package (runs on top of HTTPUnit).
> 
> Eric
>
Thanks Eric, had a quick look this morning at Canoo and looks pretty
straight forward and just what I need.

For anyone else that's interested here's the URL for Canoo's home:
http://webtest.canoo.com/webtest/manual/WebTestHome.html

Eliot

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: When & where to make 1st request for a Velocity generated page

[Eric Pugh <ep...@upstate.com>]

What I am doing is use Canoo (a web test package) to walk through my pages
tp get them cached..

Basically it takes an ant script that tells it how to reach each form or
page..

It is a very slick package (runs on top of HTTPUnit).

Eric

-----Original Message-----
From: Eliot [mailto:turbine@juxti.com]
Sent: Thursday, April 18, 2002 10:16 AM
To: turbine-user
Subject: When & where to make 1st request for a Velocity generated page


Hi everybody,
After starting the servlet engine, the first request to use a Velocity
template normally takes a bit of time to generate the output, but then
once this initial request has been made, all subsequent requests to use
Velocity are quicker.

I don't want any users to experience this startup delay, so I thought
the most obvious thing to do would be to have a servlet with an init
method that makes a URLConnection to a page generated with Turbine's
Velocity service. Whenever the servlet engine is started, this init
method is called and the first request to a velocity generated page is
made by this servlet and not a user.

What I was hoping is if someone could tell me if this is a sensible way
of overcoming the 1st request delay for velocity/turbine, or if there's
a better way or a universally agreed method of doing this.

Thanks in advance & even more thanks for this fantastic framework,
Eliot

--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>