On Apr 18, 2013, at 2:39 PM, Florian Fuchs <flo.fu...@gmail.com> wrote:
> 2013/4/18 Terri Oda <te...@zone12.com>: >> We're probably going to be running around with a bit of a hack job for the >> user database in the near future (either done by a student who needs it in a >> hurry or done by one of the core devs to support a student who needs it in a >> hurry) so while I don't like to design on the assumption it's going to go >> wrong, I think in this case planning for a redesign might be prudent because >> it's pretty clear we don't actually know all our requirements. > > I think in this case it makes sense to spend a more time on the API as > seen from the outside (urls, methods, json responses) than the actual > implementation. If the API is good, it's totally acceptable if the > underlying implementation will be redesigned later. I agree and I would advocate that that API model be based on the interface that you can readily get from a django database model and the django-rest-framework. There is a big advantage to being able to readily edit the model and have the corresponding changes to the interface automatically generated. Since HK and Postorius already use Django, you are not adding any significant dependancies. And you can leverage a existing code base for the implementation details. _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
