Ok, this sounds like a pretty good high level design. I can work towards this. Regarding splitting public chatter out of the message table. I have prepared patches to add_public_chatter and repeatedchatter to switch this over. Nothing else that I can see needs changing as those changes already occured when I did the CB caching work. (Well, 'oldcache' support would stop being useful, but thats ok.)
Having said that, in my trawls through the internal code archives I did come accross some nodes which ive marked with 'Dead Code' patches that i believe should be applied. They seem to be initial attempts at what I did with add_public_chatter, (insertmessage is an example.) Any thoughts? If I see stuff that doesnt look like active infrastructure nodes can I dead node them?
In reply to Re^2: Need ideas about better ways to manage private messages. (old plans)
by demerphq
in thread Need ideas about better ways to manage private messages.
by demerphq
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |