W dniu 27.04.2012 12:39, Tom Christie pisze:
Hey Piotr,
> I quickly skimmed the proposal and I noticed speed/performance wasn't
mentioned. I believe performance is important in serialization and
especially in deserialization.
Right. Also worth considering is making sure the API can deal with
streaming large querysets,
rather than loading all the data into memory at once.
(See also https://code.djangoproject.com/ticket/5423)
- Tom.
Maybe it can be done with chain of two black box generators. First
generator input are queryset (iterable sequence) and user defined
Serializer class contains how to transform single object and output is
python primitive type objects. Second is feed with this objects and
outputs serialized_string. What with nested objects - more generators?
Generators are good because we can also reuse Serializer objects ==
better performance. But like Anssi said - optimize after the code is
written, not before :)
--
Piotr Grabowski
--
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.
