Hi I tried this from the book, but got an error: @cache.action(time_expire=874, cache_model=cache.ram, session=True, vars=True, public=True)
So i tried the ideas in this post and they had miscellaneous errors. I thought things have probably changed since 2014. Then i started removing parameters from the book's suggestion and found that if I didn't include 'cache_model=cache.ram' it worked and set the expire time as i expected. So i am happy. But I'm not sure if i should be happy because i know so little about caching that maybe leaving that parameter out is bad. Anyhow, thought this might be helpful to someone else who knows as little about this as I do :) On Wednesday, 29 January 2014 at 18:20:21 UTC+10 Niphlod wrote: > server-side it doesn't make any sense, so there's no native way to do it. > It's not going to be faster than serving a static-file. > > > On Wednesday, January 29, 2014 12:53:00 AM UTC+1, James Burke wrote: >> >> I'm exploring options. >> >> I want to be able to cache my images. Client side, server side it doesn't >> matter. >> >> What is the best method to go about this? >> >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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 web2py+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/2092b4d5-b7be-48ce-b44a-522895b299f9n%40googlegroups.com.
