Malcolm Tredinnick wrote: > As soon as > you start to move to situations where your publically exposed resources > don't map more or less one-to-one onto models, things become a lot > trickier and we haven't quite solved that
Weren't custom descendants of the Resource class designed for this? I even thought they would be the more common application django-rest-interface since you can automatically map models to resources only in simple cases. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
