Hi! Thanks for your reply. I thought about it, and come up with the following comments:
On Sep 15, 11:04 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > On Sep 15, 9:11 am, pihentagy <[EMAIL PROTECTED]> wrote: > > Also for consistency and for performance reasons, is it possible to > > somehow return the same QuerySet for both items, _which are in the > > same request_? > I would suggest looking at the template fragment caching first and > foremost to see if it will meet your needs: > > http://docs.djangoproject.com/en/dev/topics/cache/#template-fragment-... It caches data in the template level. I could use it sometimes, if I can tell django NOT to cache some parts of the cache block... There is a long list of read-only objects spiced up with a little user- specific info in it... > If you really need per-request caching, I would suggest creating a > custom middleware app that sets/resets its internal state with every > call to process_request(). Since each request is handled by Django in > a single process in a synchronous fashion, you can use the custom > middleware as a static singleton in your code for the lifetime of the > request (and actually, with persistent processes, it may live a lot > longer than one request [...] Uhhh, that doesn't seem friendly for me... To be frank I expected an answer like: "oh, you beginner, why not do this one-liner" :) Storing data for a request (which is available in tags, templates and views is very important for me now) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
