You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by Thibaut Colar <tc...@qarbon.com> on 2001/09/25 22:44:33 UTC

Re[2]: Context behavior question.

Ok, that's what I thought, I can store part if it in the session if I want
to aniway, just wanted to be sure.
Thanks.

On Tue, 25 Sep 2001 16:23:52 -0700 Jon Stevens <jo...@latchkey.com> wrote:

> Turbine has the concept of a Pull Service which has those types of features.
> 
> This is something that doesn't belong in Velocity proper.
> 
> -jon
> 
> on 9/25/01 4:16 PM, "Geir Magnusson Jr." <ge...@optonline.net> wrote:
> 
> > On 9/25/01 4:20 PM, "Thibaut Colar" <tc...@qarbon.com> wrote:
> > 
> >> I have a quick question (I'm still not sure after reading the doc):
> >> 
> >> Is the context object linked to the user ("user persistent"), in the way a
> >> servlet session is ?
> > 
> > If you mean the 'VelocityContext', no, it isn't.  It's "just a class" and
> > has nothing to do with the servlet container / web infrastructure (because
> > you can use Velocity outside of the web environment...)
> > 
> >> Or is it just a temporary storage just for the current request (further
> >> request   from the same user will have a new blank context) ?
> > 
> > It's not request related formally - in the VelocityServlet base class
> > provided in the distro, the VelocityContext is created for each request.
> > You could retain and pool if you wanted to - you would override the method
> > that creates the VC.
> > 
> > Geir
> 
>