Pierre, There is nothing wrong with using a message ID as a thread ID. They are different namespaces (with an intuitive mapping for the first post.)
The problem is only that the mapping is not stable under the "restore after deleting some messages" scenario. If you expect to be able to restore messages and keep stable thread IDs, then you will need to assure that the mapping of message to thread ID does not depend on the presence of other messages remaining in the database. Richard On Apr 5, 2012, at 1:42 PM, Pierre-Yves Chibon wrote: > The idea of using the Message-ID for ThreadID (instead of a integer) is > that, if I whether I load one months or two months of archives into the > database, the link to the thread > (http://mm3test.fedoraproject.org/thread/packaging@fp.o/XU7HT5JC5GND2O4JII7MTQILLTB4IN4S) > will remain the same (so consistent urls). > >> There are other problems with threading that need to be dealt with as >> well, such as References being inconsistent across messages in the >> same thread and people who continue a thread with a new message, etc. > > For these I am not sure I can do something (at least automatically, we > could always allow an admin to edit the field). > > Pierre > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://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: > http://mail.python.org/mailman/options/mailman-developers/richard%40nfsnet.org > > Security Policy: http://wiki.list.org/x/QIA9 _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
