hi...
this is just a small braindump of things i noticed with the caching infrastructure in pylons. my app is dynamically rendering images using cairo, which i write into the response with: response.content_type="image/png" surface.write_to_png( response ) i did not return anything, because it was working fine. so when this was working, i wanted to have the images cached. @beaker_cache() did not work until i returned response.content from my action. i also noticed that etag_cache() does not work when @beaker_cache is in place. (clearly the function is never executed) it seems to be necessary to make etag_cache() a decorator too, where the key may be a callable. i am a bit undecided, if i prefer just one decorator handling this caching stuff. another requirement of my app is that most data is invalidated at fixed intervals( its a game where a "tick" is happening every 15minutes ) ( tick is similar to a turn. between ticks you only edit orders, which the game instances will execute, when the tick happens ) on irc it was pointed out, that most of this caching is not pylons business. and i should be using a caching reverse proxy, and be all set. what is the point in this caching infrastructure then anyways ? however some of these images should only be seen by the user who owns them. so one solution would be to include a hash in the url. to round this up: i am pretty surprised how easy it is to generate some cairo images with pylons on the fly, but managing the caching of them is a bit more involving. it would be nice to have a little chat with the guy who is designing the new caching stuff. my experience with webapps is pretty limited, i just got fascinated with pylons 2 weeks ago, and started implementing a game engine. and i dont see caching proxies and stuff in my great picture. -- torben Hohn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
