Re: Overhead of using django.contrib.markup vs. pre-rendered HTML field

Hi Brian, thanks for your reply! It's true that this is probably mostly a matter of personal preference/ application needs, but I agree with you that it's a good deal nowadays to trade a little bit of disk-space for some processing power. Best Regards, Jesaja Everling On 21 Gru, 18:33, Brian

Re: Overhead of using django.contrib.markup vs. pre-rendered HTML field

On Dec 21, 7:12 am, Jesaja Everling wrote: > Hi All! > > I'm wondering how expensive it is in terms of processing power to use > the django.contrib.markup filters for displaying blog posts instead of > storing pre-rendered HTML in a db field. > The Pinax blog application

Overhead of using django.contrib.markup vs. pre-rendered HTML field

Hi All! I'm wondering how expensive it is in terms of processing power to use the django.contrib.markup filters for displaying blog posts instead of storing pre-rendered HTML in a db field. The Pinax blog application makes use of these markup-filters to render HTML on the fly, for example. I