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 assume that especially with caching enabled this won't pose a problem, but it still might be advisable to store pre-rendered HTML once a new blog-post is saved. Does the reStructuredText filter introduce noticeable overhead or is it negligible?
Best Regards, Jesaja Everling -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
