On Jun 11, 10:04 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > I'm not quite sure what result you are expecting from a ticket like > that, though. It doesn't contain any sample implementation or even a > proposed API, so there's no way to possibly close such a ticket. > The way forward here is to propose an API and explain how you think this > system should behave. The reason why there's no sample implementation is that I generally don't really see how it could be done myself. The current cache-framework doesn't have any insight into the current request (right?), so it's not able to see if the content is provided via POST or GET. This is the first thing that has to be done, as far as I can see. If the user does a POST, the cache framework needs to delete the key for that specific content. Does anyone have any input on how that can be accomplished? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
