Comment by Mojah (not verified) on Fri, 2006-07-07 20:52.
The performance benefit displayed above is phenomenal. What a benefit to sites that handle 1000s of concurrent users, especially for low budget NPO’s and NGO’s who cannot afford the extra expense of higher performance servers to meet server load demands of growing communities.
I am most interested in your work for community projects we are currently working on.
Feature request… Can we have a per node cache time setting bypass of default time setting?
We would use this for pages that are 100% static and put an infinite cache time or a very long cache time like 42days. Can such pages also have a refresh cache button just in the event of an update to that page?
Thanks for the work
One Love
»
Reply
About Me
I’m a twentysomething coder living la vida loca on the southern coast of Spain. I work primarily with Ruby on Rails and Drupal, and dabble in the dark art of Lisp programming for my own amusement.
The performance benefit displayed above is phenomenal. What a benefit to sites that handle 1000s of concurrent users, especially for low budget NPO’s and NGO’s who cannot afford the extra expense of higher performance servers to meet server load demands of growing communities.
I am most interested in your work for community projects we are currently working on.
Feature request… Can we have a per node cache time setting bypass of default time setting?
We would use this for pages that are 100% static and put an infinite cache time or a very long cache time like 42days. Can such pages also have a refresh cache button just in the event of an update to that page?
Thanks for the work
One Love