This seems like a silly question to me, but what is considered the
scope of a request vs the scope of a session? Which is longer?

I'm trying to figure how to go about having an object fetched from the
DB in memory so I don't have to fetch from the DB every time someone
submits the form. In my case, I would like to have a search involving
zip code that has some associated info in the DB that I would need for
distance calculations, and I would like to keep that DB object around
until the user clears or changes the zip code field, making the
fetched object obsolete.

I am considering using sessionmemoize or requestmemoize objects to
suit my needs, but I don't know how long each one would stay around (I
can't think of concrete examples of request vs session...I always
though request happened every time you clicked a link to go somewhere
on a webpage, whereas session is as long as the browser is on the
site).

I've also considered a stateful snippet, but I don't think that's the
right way to go about it since there is no clear start and finish to
the snippet from where to unregister from.

Thanks,
Strom

-- 
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en.

Reply via email to