On 9/7/07, Joshua 'jag' Ginsberg <[EMAIL PROTECTED]> wrote: > Problems: > 1) While there is a good degree of drop-in replacability of parts in the > Django stack as I outlined (db backend, authentication backend, etc.) there > is not a clean way for programmers to grok what specific contract various > components have to comply.
Personally I'd rather solve this with documentation. > 2) There is not replaceability for every component unless such > replaceability is specifically engineered in by the Django team. Sure there is. Want an alternative session component? Import it and use it according to its documentation. > 3) Without some sort of agreed upon standards to support interaction between > apps, we will not be able to harness the wealth of django apps being written > right now into complete, integrated sites. I dunno, I've managed it pretty well. Offhand I'd be -1 on anything that makes Django's codebase more complex; there are very few things that can be solved by "component interfaces" that can't also be solved by good documentation, and the documentation carries a lot of other benefits with it besides that. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
