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. Florian _______________________________________________ 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
