It's also not clear to me what "(not) supporting Ajax" would even mean.  Ajax 
just sends HTTP requests, and the server responds to them (usually with JSON 
structures).  I have tons of Ajax applications that use Django as the backend, 
so if it doesn't support it, no one tell that code lest it stop working. :-)

On Jun 29, 2013, at 12:05 PM, Russell Keith-Magee wrote:

> 
> Can you provide a little more direction than "The website"? "The website" is 
> a kinda big place… :-)
> 
> Yours,
> Russ Magee %-)
> 
> On Sat, Jun 29, 2013 at 2:08 PM, Gamesbrainiac <[email protected]> 
> wrote:
> Then why does itsay on the website that Django does not support Ajax natively?
> 
> On Jun 29, 2013 12:03 PM, "Russell Keith-Magee" <[email protected]> 
> wrote:
> 
> I'm not sure what you mean. Django completely supports AJAX right now. 
> 
> Django is a server-side framework, and the only part of AJAX that is 
> server-side is the API call. 
> 
> An API call is just a view that returns JSON/XML instead of HTML. You can 
> write that right now in Django.
> 
> If you want a library to make it even easier, there are several options, 
> including TastyPie and Django-REST-Framework.
> 
> The client-side part of the AJAX problem is outside the domain of Django. 
> There are plenty of good client-side frameworks; pick one, and you'll find it 
> can talk perfectly well with Django.
> 
> Yours,
> Russ Magee %-)
> 
> On Sat, Jun 29, 2013 at 1:52 PM, Nafiul Islam <[email protected]> wrote:
> In which version, will Django natively support Ajax? I'm curious because you 
> need Ajax for almost any site these days, and Django not supporting it 
> natively has become a bit of a hindrance for me.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/django-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Django users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/django-users/2oaiisZw_ZY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
> 
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/django-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/django-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/django-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

--
-- Christophe Pettus
   [email protected]

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to