> Can you be specific on how the current setup is preventing you from > getting it done?
I think the easiest way is to look at my code on bitbucket, for example my models.py: https://bitbucket.org/bolhoed/django_disqus_comments/src/b2c6fbb025f6/models.py. As you can see, I have to hack my own model manager and queryset, just to be able to use the Disqus API instead of models on the local database. > Apart from a model backend what other backends are we looking at to > store comments? Whatever you would want. If you make abstract base classes for getting comments for an object, getting the count of comments, and saving a new comment, everyone could make their own backend. You could use Twitter for comments (with a hashtag), Disqus, a nonsql database, textfiles... However, I would only ship the models backend by default. > If it is a clean proposal, it might be possible to convince the core > devs to break the backwards compatibility rule. You can count me in > for any kind of help regarding this task. Cool, thanks. I think my basic idea should be pretty clear: just offer an extra layer of abstraction above the ORM for the comments. I am not sure what the best way to do this would be, but I should have plenty of time this week to look into it. Cheers, Kevin -- 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.
