Hi, Short version: the effort you put into saving that CPU and RAM and bandwidth is undoubtedly better spent on implementing an actual HTTP caching layer which will give you a much more powerful, scalable and generic (= reusable, tested, etc) solution. It will also keep your code short and clear (= less bugs, easier to maintain, read, etc). I use Squid as an example.
Long version: we should probably agree on the fact that we will never agree anyway in the first place, and I am quite willing to draw short on this. I know that my view is not a popular one, and I know that stop-gap solutions are always favoured over more elaborate but arguably also more appropriate solutions. Unless, perhaps, if the status quo has it that general consensus is clear on this (see plethora of programming dogma's, "goto" as a notorious example). And I am probably not right. Given that, if you or anybody else still want to discuss this, I am more than willing to join you. Although we should perhaps do that in a separate thread :) Greetings, Hraban 2010/12/11 andrei <[email protected]>: > > On Sunday, December 12, 2010 12:47:29 AM UTC+3, Hraban Luyat wrote: > > In which case you do not need caching in the first place, not in your > either. > > Here you assume resizing image on fly and streaming it is ok. How is this > better than saving the resized file and serving it as static? > Even for website that doesn't experience high load this operation costs > quite a lot of cpu and ram, having Squid setup just for this > is overengineering. > > -- > You received this message because you are subscribed to the Google Groups > "web.py" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/webpy?hl=en. > -- You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/webpy?hl=en.
