First of all: my native language is not English, so I apologize for any potential natural language error (or any error at all) below.
After (briefly) reading through the current implementaion as well as the "Issues to consider" section in the GSoC2011 page on wiki, my initial observation is that the current code structure/abstraction is almost good enough to cater all the "Issues" on the wiki if The need for "Serializing non-database attributes/properties" is not considered for now. It seems to me that an simple enhancement on the configuration options of the current serializer would suffice a lot of the needs here. The best approch I thought of so far is adding a configuration object to the parameter. It contains infomation about what modification needs to be done during the serialization. Does any field name needs to be mapped to a different one? How many levels to go as far as foreign key is concerned? What are the unnecessary fields (of course, the current "fields" option would fit well in here, too)? What are the relations between two fields in the result? This configuration object will be available to all the subclass-serializers for different format all the time, so that everytime a field is being serialized, the serializer will look for infomation the configuration object recarding this field. Further, when a fk is encountered, the configuration can contain reference to another configuration object, which, if desired (level of serialization not yet reached), will be used to serialize the object fk refers to. Naturally, the configuration object should be defined with classes (I almost wanted to call it Meta, as in the Models). I feel like I'm still missing a lot to consider. I'm aware of the old proposals in the past and I'm planning to digest those as soon as possible. But I really want to hear thoughts about my idea from y'all. So please, tell me what's wrong in it. PS: I have about 3 years Python experience, big Django fan, sort of a user (wrote my own blog, of course), my ID has appeared in Django commit msgs for about 3 times so far :). -- You received this message because you are subscribed to the Google Groups "Django developers" group. 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.
