When looking into JEP (now XEP) 136, message archiving, I noticed that someone had written a patch to allow pyaim-t to archive messages through datasink.
I wanted to voice a slight concern that this functionality is misplaced. The main idea behind the JEP seems to have message archiving tightly controlled by the user with a good deal of client interaction. It would seem that the capability should be integrated into the client in that case. The JEP offers a server-side alternative, automatic archiving, but this seems focused mainly on cases where such archiving is mandated by organizational policy. In any case, the automatic option is for implementation on a server-wide basis and not protocol-by-protocol. This may very well be a case where you guys throw ideals to the wind for the sake of the real world, which is fine. I just wanted to raise this concern. In ideal terms I don't believe such functionality belongs in a transport, but then again not many clients have picked it up. See http://www.blathersource.org/features_view.php?projid=pyaim-t&featid=59 and http://www.xmpp.org/extensions/xep-0136.html And of course I'm completely appreciative of counsellorben for his contribution. Huzzah! ~Chris _______________________________________________ py-transports mailing list [email protected] http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
