ah ok. mine was for making it sure that the first user "waits" for the page to be rendered and cached, while all subsequent users will fetch the already cached value. Stick with a 86400 (better to shave off some seconds, like 86300) and in your crontab fetch the page (curl, urllib, webclient, whatever) every day at 00:05. In that way your "program" will act as a user requesting the page at 00:05 so web2py caches it for the entire day.
On Sunday, April 14, 2013 3:02:34 PM UTC+2, BlueShadow wrote: > > thats not what I wan't. > I don't want the user to load the page and wait for it at all. (because > eventually it will take half an hour) > > I want that web2py is the first user who loads it every day. So that when > I access the site lets say at seven o klock the side is already cached. > > On Sunday, April 14, 2013 2:49:21 PM UTC+2, Niphlod wrote: >> >> it's 24 hours every day. the point is that you need to cache it for 86400 >> seconds only if it's 00:05 in the morning. >> if it's 00:10, you have to substract 300 seconds from 86400, and so on. >> >> -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
