Thursday, Feb 09, 2006 at 18:44
Thanks Mike,
The show changed bit since last
logon is a few days away for members. I already track last
logon dates and provide members with a what has changed since last
logon however as you mention it does not help with the parts of the thread that have changed since last visit. This is going into members in a couple of days. (I will be showing already read thread parts with a different background color - when using last
logon search). As for visitors I will see what the results are from member
feedback as to how it is received and then look at my options.
I currently do not track last
logon for visitors so there would be a few mods to make around the system, not imposible but I do try to give members a little more, and certainly give it to them first.
To show the status of each thread for each person as you have read it is a little harder and would require a bit more DB space to track the read/un-read status of every thread for every reader - Now this is not that hard a task just DB expensive 1000 active threads, date/time of last read/thread = 8 bytes * 1000 = 8K (approx) X 20,000 visitors = upto 160MB of tracking elements * 40c/MB DB space/Month = $64/mth just for this tracking. Using cookies is another way however large cookies slow things down as they are passed with every request and this also costs in traffic. Again if I shrink the list to a members feature I change the possible 20,000 to 1,100 then DB space is 8.8MB = $3.52/mth. I know it does not sound like much but all these added to the already large hosting, DB and traffic charges force decissions to be made.
Let me think about this some more and I will see what I can come up with. Nothing is out of the question - just has to be planned, costed and installed. Thanks for the feeback.
FollowupID:
408059