Rails/Django creates the html files and the webserver serves one of
those or calls django if there is none that matches the request.
For example if someone requests "domain.com/blog/2007/13/12/my-god"
than there would be a folder somewhere in the filesystem where the
file "/blog/2007/13/12/my-god/
If it is Django/Rails who is doing the thing, the server *has* to run
it. So it's nonsense speaking about mephisto doing that. The deal would
be in apache taking care of it.
El s�b, 22-09-2007 a las 17:26 +, julian.bash escribi�:
> Thanks a lot for your answers!
>
> The even greater thing w
On Sep 22, 2007, at 10:26 AM, julian.bash wrote:
>
> Thanks a lot for your answers!
>
> The even greater thing with funky caching is that the webserver only
> has to serve html (if there is a cached version) and doesn't have to
> run django. So, django's normal caching is good, but when the serve
Thanks a lot for your answers!
The even greater thing with funky caching is that the webserver only
has to serve html (if there is a cached version) and doesn't have to
run django. So, django's normal caching is good, but when the server
only has to serve already-generated html-files, the whole t
> "you redirect 404 errors to a script, which looks at the requested
> URL, decides whether it should actually exist, and if it should it
> builds the file from the database, saves it to the filesystem, and
> then returns the page to whoever requested it. Next time that URL is
> requested, the sta
That's more or less how flatpages work. Have a look at their middleware.
El s�b, 22-09-2007 a las 05:40 -0700, julian.bash escribi�:
> Hi!
>
> Does anyone have an idea how to implement funky caching with django?
> For those who don't know what that is (it's simila
Hi!
Does anyone have an idea how to implement funky caching with django?
For those who don't know what that is (it's similar to how movabletype
does caching but doesn't prepache everything):
"you redirect 404 errors to a script, which looks at the requested
URL, decid
7 matches
Mail list logo
