This is the final progress report for my project, Authenticated REST API
for Postorius/Django.

The code is available at https://bitbucket.org/mgill25/mm-rest

I'll go over the major points of the work done so far:

* The public-facing REST Interface is mostly done. Most business use
cases, things like creating/deleting
lists, subscriptions etc are working via REST.

* The REST Interface currently works with Basic Auth, but other
authentication schemes are easily pluggable
via the Django REST framework.

* Postorius has been modified in order to use the MM-REST models instead
of directly interacting with
Mailman Core.

* Hence, in the case of no connection available to Core, MM-REST, and
consequently Postorius,
continue to work on their own, saving data in their own level. Which
brings me to...

* The Caching Interface b/w Mailman Core and MM-REST, which is yet to be
completely finished.
I have a (somewhat) generic interface, but haven't managed to make it
work for all the models, primarily Memberships.

* Workaround in mm-rest or modifications in Core for allowing backing up
of certain Models,
which is currently limited by the Core REST API. For example:
Registering new Email addresses for a User.

* And there's a small todo file in the project containing some things to
be done yet.


The project is not 100% finished yet, and after the GSoC is formally
over, I shall continue working on it.



Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Mailman-Developers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Reply via email to