Kaylan, Good point. That would have to be a part of the specification 100%. Any foreign key table entries that are "folded in" would have to check out with the permissions component.
On Mar 31, 6:24 pm, Kalyan Lanka <kalyankumar.la...@gmail.com> wrote: > I am not a Django developer but have been closely following this group as I > have been in love with Django framework since I started using it. You guys > have done a great job. > > > > > 6. Proper Links / Foreign Key Resources > > If the request for primary key starts our sending out "foldable" foreign key > related objects, it can cause some security issues for the application. For > example I would like to send about a person information but not all their > addresses. I think it would be good if the spec. provides hooks so that the > developer can customize based on the role of the consumer on how deep the > response can go. --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
