I'm sorry, but I can't agree. I've used DWR as well, and the "server generates your Javascript to include" model really creates a lot of problems, both with versioning and performance.
Simple is best. I've had the best luck with straightforward use of the prototype.js Ajax class. Regards, -scott On Sat, 2006-06-03 at 12:05 +0100, Derek Hoy wrote: > I used DWR for a java project I finished last year - > http://getahead.ltd.uk/dwr/ > > It really simplifies the client-server ajax stuff. It lets you fetch > an object from the server and have it available in the client as a js > object, with properties and methods all available in your client code. > DWR serverside code generates the js files for download to the client > that handles all the marshalling stuff, so you don't see any of it. > > It would make a great model for ajax support in Django. You call a DWR > js function, giving it a callback to your js function. This function > gets an object as a param, you use the object to fill bits of your > page etc. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
