Thanks for the comments, Steve - can you clarify what you mean by a "write-only API"? As far as I can tell I could use that to insert messages that Mailman now considers "posted to the list" into my own DBMS and then present them however I like. I'll have a bunch of questions around robustness and error handling, but is that not basically the case?
I like the idea of Hyperkitty returning fairly plain HTML that I could later style, although having a REST API that would allow me to get at thread objects which contained a tree of message objects would probably be ideal. I suspect that's fairly trivial for me to implement assuming my assumptions about IArchiver are correct. Cheers, Colin On 8 November 2013 23:20, Stephen J. Turnbull <step...@xemacs.org> wrote: > Colin Fleming writes: > > > Is there a way to create an archive view (i.e. present a view of > > all messages in a list and allow reading particular mails) using > > the current API? > > No, and (sorry Barry, but I think you just added to the confusion -- > IArchiver is really a write-only API) there won't be unless the > architecture of Mailman 3 changes dramatically. Archiving (storage > and retrieval of posted messages) is the responsibility of a separate > module. What Mailman itself can tell you is the suggested permalink > for individual archived messages. > > We do plan to provide such a module (the current implementation and > leading candidate is called HyperKitty). > > I do not know if the current architecture of HyperKitty is > sufficiently modular as to allow you to just grab messages and then > format them yourself. > > I'm not sure why you'd want to grab raw messages, actually; I think > the best idea would for HyperKitty core (or any other implementation > of an archiver) to spit out a DIV element containing the > (semantically) formatted email message, and provide a default CSS, > plus a fairly trivial full webapp that wraps the DIV in a full page. > I'm not sure if it does that yet, though, you need to talk to the > HyperKitty devs about it. > > (Heck, if it doesn't, maybe I'll go into the archiver business > myself. Look for CSSZenKitty at a DVCS host near you!) > > Steve > > _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org 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
