-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 22.03.2015 um 02:32 schrieb Barry Warsaw:
I want to make some minor backward incompatible changes to the JSON representation for pending mailing lists requests, e.g. subscription holds. You'll see these for example in urls like:
dump_json('http://localhost:9001/3.0/lists/ant@example.com/requests ')
entry 0: delivery_mode: regular display_name: Anne Person email: anne@example.com http_etag: "..." language: en request_id: ... type: subscription when: 2005-08-01T07:49:23
The first change is that
type: subscriptionrequests will change theiraddresskey topasswordkey.Let me know if this is a problem, and I can copy
addressso that both would appear, and add a dummypasswordkey.
As for the password key: It's recognized by mailman.client and
exposed within the mlist instance's requests property. But it's used
nowhere in postorius and I would be surprised if it's used anywhere in
hyperkitty (Aurélien...?). I guess it can go away.
As for the email/address keys: We can also just keep the address key
in mailman.client and let it use the same value as email. That way
we would still have a fallback but the REST API would stay clean and
wouldn't send any redundant information over the wire.
Can you notify me when your API changes are pushed to LP, so I can update mailman.client accordingly? Just to keep the window as small as possible where we have non-compatible states in the mailman/mailman.client trunks. Especially during GSoC application week...
Florian
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEcBAEBAgAGBQJVDyxKAAoJEEceGbPdavl7VicIAIvPKbwYfpAHDHBDNHjQALjZ eTjz1KjaH/q9cyAQ1rmhttH1emiz5BukKOIvUTxeANc8ooscHXmUN+Prs1ahgebe tSS7lKvc14kx9QW1HRvbQdnQpYcicNyTSZhTjeD/+RDIaUE+MWaRRxGbcOkHXCHT OrmXeBSOAYGHPrNsExUcIBwRz8IdjFajQ8FIYS/GddsFeotUBJfQxQ7xdkDJMYkB 6iuPtuWwEKXvbxZLMgPtpCpuxYxOeS+cfQarXCdXLmrwruYNDPK0T16TQOa+QC+o /3oNR5aKOTWmy3Dg+Jf2+CJ2eKmQ/NPqvWotXkl2h5CdwWu+TB8RZBTA3XQ91Z4= =v1VH -----END PGP SIGNATURE-----