REST access to preferences

Bug #821438 reported by benste
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNU Mailman
Fix Released
Medium
Barry Warsaw
GNU Mailman REST Client
Fix Committed
Undecided
Unassigned
MailmanwebGSoC2011
Triaged
Wishlist
Unassigned

Bug Description

Using the Python bindings the following things are available at the moment:
self_link: u'http://localhost:8001/3.0/members/2'
role: u'member'
user: u'http://localhost:8001/3.0/users/2'
address': <email address hidden>'
fqdn_listname': <email address hidden>'

For better user management the following options should be seen as wishlist:

acknowledge_posts
hide_address
receive_list_copy
receive_own_postings
delivery_mode
delivery_status

in addition i requested _User.get_lists which is in https://bugs.launchpad.net/mailmanwebgsoc2011/+bug/821069

+ what about users password ? users e-mails ...

Tags: mailman3
benste (benste)
Changed in mailman.client:
status: New → Confirmed
tags: added: mailman3
Changed in mailmanwebgsoc2011:
status: New → Triaged
importance: Undecided → Wishlist
Barry Warsaw (barry)
Changed in mailman:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Barry Warsaw (barry)
milestone: none → 3.0.0a8
Revision history for this message
Barry Warsaw (barry) wrote :

Actually, these are going to be interesting, because individual IMember preferences are stored in multiple places, and there's a _lookup() method that returns the first non-None value. This would probably be fine for read-only access, but if you want to write changes, where do you write them? I think that if you POST or PATCH any of the attributes, it changes them on the member directly (i.e. overriding any other value).

Barry Warsaw (barry)
summary: - REST and Client are missing membership_settings options
+ REST access to preferences
Barry Warsaw (barry)
Changed in mailman:
status: Confirmed → Fix Committed
Barry Warsaw (barry)
Changed in mailman:
status: Fix Committed → Fix Released
Changed in mailman.client:
status: Confirmed → Fix Committed
milestone: none → 1.0.0a1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.