<snip> I need some design advice. The first question is about threading. Lets say that a list post starts off with one subject and then changes to another subject. The new subject is still in response to the old subject but may deal with something new. i.e. a thread starts out about MM sales practices and then changes to a talk about CF & DNS. The threading (i.e. message in response to what other message) is intact but the subject changes half way through. Should each thread be its own entity, even with subject changes or should a subject change make it a new thread? </snip>
Would it be possible to have some sort of reference to the original thread, but treat the new subject as a new thread? My thoughts are that if you can provide a reference to the original thread then it would make sense to have a subject change become a new thread. But sometimes it's useful to know how a conversation got to where it is. (grasping here, but maybe something like "Derived from: Another Thread - Click here to see it." somewhere in the new thread.) Otherwise, the (WAS: Another Subject) convention has been working for me - I understand the shift in topics, and can still track back if needed. Thanks Michael. Looking forward to the changes, and appreciate your hard work. Shawn Grover ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
