On Thu, May 7, 2009 at 5:18 PM, daonb <bennyd...@gmail.com> wrote:
>
>>  * Builtin support for the full Atom publishing protocol. This is
>> already logged as ticket (#3569) and was originally accepted for v1.1,
>> but got delayed in the interest of the schedule.
>
> Makes sense to support RFC 4287. I think it will help if we drop RSS
> support and support only Atom. I'm +1 for dropping RSS support.

While Atom has many advantages over raw RSS, RSS is still a widely
accepted and understood format. I think it would be premature to drop
support for it. It shouldn't be too hard to accept both - just like we
already do.

>> * Named URLs for feeds
>
> Sure.
>
>>  * Deploying at arbitrary URLs, rather than /feed/<x>/<y>/<z>
>
> Yep.
>
>>  * Member per-feed permissions
>
> Maybe we can associate each feed with a list of groups, so that only
> group members get access.

This sounds like almost exactly the wrong thing to do.

Look at permissions everywhere else they are implemented in Django -
it's a function. For standalone views, this is a function that returns
true/false when the resource is visible; this function is then wrapped
in a decorator. In the admin, you override functions on the base site
to control resource visibility.

These functions can access contrib.auth tables if necessary, but it
could equally evaluate any other function based on any other
parameter.

I would expect that on a feed, you would either override a base
visibility function that returned true/false, or the method that
turned a request into a feed item could raise PermissionDenied
exceptions.

Yours,
Russ Magee %-)

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to