If you're looking for a portable way to write temporary stuff on the file
system from a servlet,
File tempdir = (File)
getServletConfig().getServletContext().getAttribute("javax.servlet.context.tempdir");
alex
On Sun, Dec 7, 2008 at 2:25 PM, John Nilsson <[EMAIL PROTECTED]> wrote:
> Use Varnish?
>
> http://en.wikipedia.org/wiki/Varnish_cache
>
> BR,
> John
>
> On Sun, Dec 7, 2008 at 10:31 PM, Tim Perrett <[EMAIL PROTECTED]> wrote:
>
>>
>> Hey guys,
>>
>> Im looking for a little bit of advice regarding a home rolled caching
>> system. As you've probably seen in my other posts, im building a
>> system that loads templates from the database. This is all going
>> swimmingly now, and im looking at how to best cache the markup so that
>> the database is not being hit on every request.
>>
>> Now, I have got all the stuff working to grab the markup after it
>> served once - im just trying to decide how best to write it someplace
>> so that it can be served by a front end server (apache, nginx etc). I
>> could persist it to the filesystem at a point defined in the
>> application configuration, but this somehow feels a little hacky. I've
>> thought about how the containers expand the WAR files, and im
>> wondering if there is a more elegant solution possible in which the
>> users wont need to worry about filesystem permissions and things?
>>
>> Any ideas / advice appreciated :-)
>>
>> Cheers
>>
>> Tim
>>
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
