On Thu, 2009-02-19 at 20:39 +0900, Russell Keith-Magee wrote: [...] > Regardless - protocols like this can (and, for the most part, should) > exist as external projects. James Tauber's approach with > django-atompub is exactly the right idea. If you particularly want > MetaWeblog support, it doesn't need to live in Django's core. Hunt > around to see if anyone else has implemented it, and if they haven't, > start a project. In time, if you create a robust implementation and > can demonstrate demand for it, it may be considered for inclusion in > django.contrib. Until then, it can live happily in the ecosystem > without requiring any official blessing from us.
Also keep in mind that one of Django's goals is encouraging and enabling "best practices" where such things exist, particularly when looking at things for contrib. Atom sydnication and Atom publishing are standardised protocols that have gone through the IETF process and are used in lots of situations, weblogging being only one example. The Metaweblog API has not had the same level of standardisation and is targeted at blogging-style applications exclusively. It's also RPC-oriented, rather than REST-oriented, which isn't particularly good practice in a web-oriented domain space. Atom publishing is always going to have an edge in situations like that, simply because it's a more appropriate general protocol. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
