Jay Parlar wrote: > This was using the dev server and DEBUG=True. Maybe I missed something > in terms of how to get useful output, but it'd be nice if there were a > decorator or something that could tell Django that the client > expecting a response is *not* going to be able to display that > response, and the exception info should be displayed on the terminal.
Well, assuming you implemented it with a simple 'RESTful' ping-a-URL-and-get-something-back view method, you can easily debug it by finding out what exact URL the JavaScript accessed (pretty sure runserver tells you this on the console?), and manually going there in your browser. Then you will see the normal Django error message. Took me a short while to figure this out myself, probably because it was so simple it didn't even occur to me at first =) As for the general AJAX discussion, I agree wholeheartedly with James--there's no need to tightly couple a given framework, especially since good AJAX is exactly what he suggested and what I, at least, have used successfully--the JS framework on one side and RESTful Django views that return JSON or XML data on the other side. Unless you (theoretical 'you', nobody specific) are doing something extremely thorny (in which case you shouldn't expect the framework to do everything for you *anyways*), this setup will work beautifully and will make it super easy for people to use whatever JS framework they so desire (I currently use Dojo, for various reasons). Regards, Jeff --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
