Hi Tom, I've knocked around ideas of my own (internally, and on #django) related to serialisation: it's something I've had lots to think about, since until recently, most of my django work was in JSON apis.
I personally think that Forms are already the place that should handle (de)serialisation. They already serialise to HTML: why should they not be able to serialise to other stream types? This is the approach I've started to use for my API generation code. They already have a declarative nature, and then you get all of the form validation on incoming data: a big improvement over how I've done it in the past. (I've done some work on a form-based API generation framework: https://bitbucket.org/schinckel/django-repose. Whilst this is in use, it's still not really feature complete). Matt. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/bduEvNY0oUkJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
