[eluser]andrewtheandroid[/eluser]
hi jedd first of all thanks for taking the time to read my post.
Quote:I'm not sure from your code sample and subsequent explanation was an adjustment of my idea, or an extrapolation of your original ..
I think I may have not worded my reply as well as I hoped. I think when I went and edited it I took out the "I like the idea of.." to indicate it was not novel. Yeh as i was reading I was thinking of which of the ideas I would try to use for my project. Not my own "new" solution to the problem. Sorry.
Quote:Lets say we are only really interested in the last (say 30) topics.
As soon as you set arbitrary limits for things like this, you strike a whole raft of new problems I think.
I see how a busy forum with many new topics each minute would be a big problem but then again I set the arbitrary number because I think we need to set a line so it won't cause a problem for performance? Also if there were 100 new topics that were 5 pages deep I think anything past 2 pages is not as 'new' it is true I haven't read them but then if i dont visit the forum in one month I don't want to be flooded with 100 new topics as unread. I think anything older than an arbitrary figure whether it be a few months or x number of new topics?
I only did a database unit in uni so I have no real experience when it comes to real world performance of something like that. I'm genuinely interested to know what kind of problems that would cause. Would it be a performance issue? or a maintenance issue? etc..
Quote:In any case, I can't see any advantage to tracking via time rather than message number.
That's true about the difference in time and that message id would be the same..
So if i were to use messageid in place of dates in my description it could work?
Quote: There's probably a few things that will be hard for me to implement later, but I think I got most of the interesting functionality sorted (or at least sortable).
I'm not going to be too ambitious for this project since the maximum number of people that can join is 1000 seeing as it's an employee website. I doubt that they will all join I think the max I would probably see would be 400 or so. If that's the case would performance be a big issue here with my implementation?
Also is this read vs. unread feature a must or a "nice to have"? Just want to know how much attention to detail i should give this for the project.
Thanks again for feedback.
