So far the discussion of "AJAX support" in Django has been a relatively contentious one. There seem to be two viewpoints at the heart of this conflict, which are not mutually exclusive in their substance. At the risk of being unfair, let me grossly generalize the two positions.
1. AJAX is the future, and Django should be on board. AJAX may be overhyped, but it's hyped for a reason. AJAX is a core component of developing modern Web apps, and as a modern web framework Django should support AJAX as a core feature. 2. Django already has all the AJAX support it needs.''' As a backend framework, Django needs to provide data in a standard way that's easily consumable by any AJAX toolkit (following the rule of loose coupling). Since choosing wizzy frameworks is becoming a web development holy war, Django should support any of them. The root of the conflict here seems to be traceable to the fact that AJAX, like pornography, has no clear definition. You know it when you see it, and everybody sees something different. With that in mind, let's see if we can work together here to get a consensus on the goals of AJAX support in Django. I've collected some of the posts from the list discussions onto a wiki page that I hope will serve as a starting point. http://code.djangoproject.com/wiki/AJAX This is a naive attempt on my part, since I'm not a programmer, but I am anxious to see this discussion move beyond (ahem) lively discussions and into the realm of practical solutions. I hope all of you with both an understanding of and an interest in this will take it and run with it. Cheers, Wilson
