Adrian, There are so many things about this that I cannot think of and, hopefully, David will be able to comment. The InstanceOfContentId field is used in a mode where content is derived from a template. I don't think that there would be any conflicts in its use, but I am guessing the right philosophy is that if it is needed, you should add another field to the entity.
The ownerContentId is another field that could be used. I have used it for that purpose before. It is suppose to be used to identify the content record from which security permissions should be determined and, generally, that would be the content that starts a thread. The only place that that would not work is if in the middle of a thread, two or more parties wanted to send private messages to each other. But if that were the case, it would probably constitute a new thread. I think I would lean towards adding a new field, then it would be the use of ownerContentId and then instanceOfContentId. But, like I said, I am not certain enough about any of those options to be definitive. -Al On 8/23/07, Adrian Crum <[EMAIL PROTECTED]> wrote: > > I think I've mapped out the basic entity usage for forums. I wanted to see > if it's okay to use an > unused field to hold the forum thread ID. I know I can start with any > ContentAssoc record and walk > up the tree to find the ID of the uppermost message (the thread start) but > since forums (and > threads) can contain thousands of messages this approach is far too > inefficient. > > Currently the Content.InstanceOfContentId field isn't used in forum > messages. It seems like an > appropriate place to store a thread ID, since the message can be thought > of as an instance of a thread. > > What do you think? > > -Adrian > >
