Comments on: Why you should use Caching in your webapp. http://coderseye.com/2007/why-you-should-use-caching-in-your-webapp.html Programming is passion made real Fri, 09 Dec 2011 00:27:29 +0000 hourly 1 http://wordpress.org/?v=3.1.1 By: john speno http://coderseye.com/2007/why-you-should-use-caching-in-your-webapp.html#comment-460 john speno Thu, 23 Aug 2007 14:17:08 +0000 http://coderseye.com/2007/why-you-should-use-caching-in-your-webapp.html#comment-460 Brilliant! Tack själv. Brilliant! Tack själv.

]]> By: Fredrik http://coderseye.com/2007/why-you-should-use-caching-in-your-webapp.html#comment-459 Fredrik Thu, 23 Aug 2007 11:40:09 +0000 http://coderseye.com/2007/why-you-should-use-caching-in-your-webapp.html#comment-459 "Is that something that django has been made to do yet?" Why not just use "wget --mirror" against a staging server, and a suitable apache configuration? “Is that something that django has been made to do yet?”

Why not just use “wget –mirror” against a staging server, and a suitable apache configuration?

]]> By: john speno http://coderseye.com/2007/why-you-should-use-caching-in-your-webapp.html#comment-458 john speno Wed, 22 Aug 2007 16:37:24 +0000 http://coderseye.com/2007/why-you-should-use-caching-in-your-webapp.html#comment-458 Yes. It writes out static pages like product_one.html with links to static images on disk etc. Any part that needs to be dynamic still is (e.g. the cart and admin interface) and it's more than just a PayPal frontend. :-) For a small store it's quite nice, but I imagine it wouldn't scale well for larger stores that would need to rebuild their static pages frequently. We do it only rarely and it only takes a few minutes to build just over 300 static pages. On a dedicated server I probably wouldn't even bother. Yes. It writes out static pages like product_one.html with links to static images on disk etc. Any part that needs to be dynamic still is (e.g. the cart and admin interface) and it’s more than just a PayPal frontend. :-)

For a small store it’s quite nice, but I imagine it wouldn’t scale well for larger stores that would need to rebuild their static pages frequently. We do it only rarely and it only takes a few minutes to build just over 300 static pages. On a dedicated server I probably wouldn’t even bother.

]]> By: Bruce http://coderseye.com/2007/why-you-should-use-caching-in-your-webapp.html#comment-457 Bruce Wed, 22 Aug 2007 15:26:51 +0000 http://coderseye.com/2007/why-you-should-use-caching-in-your-webapp.html#comment-457 Hm. Somewhat, I suppose. You can choose to use a file cache and give it a long timeout. But I don't think that is quite what you mean. You are saying that your package can write out a set of static pages and they'll work with no dynamic backend? If that's the case, then no. I personally wouldn't use such a feature except in rare cases. The store needs to be dynamic, not only on the front-end, but on the back, tracking inventory, referrers, and providing access to the admin pages. A static set of pages would be only useful as a generator for a PayPal cart or something similar. Hm. Somewhat, I suppose. You can choose to use a file cache and give it a long timeout. But I don’t think that is quite what you mean.

You are saying that your package can write out a set of static pages and they’ll work with no dynamic backend? If that’s the case, then no.

I personally wouldn’t use such a feature except in rare cases. The store needs to be dynamic, not only on the front-end, but on the back, tracking inventory, referrers, and providing access to the admin pages. A static set of pages would be only useful as a generator for a PayPal cart or something similar.

]]> By: john speno http://coderseye.com/2007/why-you-should-use-caching-in-your-webapp.html#comment-456 john speno Wed, 22 Aug 2007 13:10:18 +0000 http://coderseye.com/2007/why-you-should-use-caching-in-your-webapp.html#comment-456 There's a feature I like in the e-commerce app I've been using for the past few years. It allows us to build a static version of the site with all the pages written out to disk. That makes things as fast as possible. Is that something that django has been made to do yet? There’s a feature I like in the e-commerce app I’ve been using for the past few years. It allows us to build a static version of the site with all the pages written out to disk. That makes things as fast as possible. Is that something that django has been made to do yet?

]]>