>>Why would you want to access "messages scheduled for archiving” via REST? I >>have trouble imagining a use case.
It would make it pretty easy to write an archiver if all I had to do is poll via the REST API for new messages waiting to be archived whenever I feel like it and put them somewhere. Clearly that’s not going to work if the emails are being shunted out the door to some other archiver via the existing archiving interface. But if that could be addressed somehow, REST API access would make life pretty easy for dealing with archive messages - mainly I’d like to avoid touching the Mailman core or write anything that needs installation into Mailman. I’m not sure exactly what I have to do to write something that interfaces to the core archiver so I’m not sure how easy or hard that would be. as On 16 Feb 2015, at 12:57 pm, Stephen J. Turnbull <[email protected]> wrote: Andrew Stuart writes: > Is there any reason why it should not be possible to be able to > pull messages scheduled for archiving out through the REST API as > file attachments? Oops, my previous message missed the subtlety that you do have the message at the point in time you're considering. You still can't do archiving with REST: REST is a "pull" interface, archiving is a "push" operation. Why would you want to access "messages scheduled for archiving" via REST? I have trouble imagining a use case. _______________________________________________ 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
