It seems like the "Iv'e checked all these" button updates the time from the user's local machine. This may lead to wrong results as if this button is pressed after few other messages have been posted elsewhere, they will not be seen by the user.
To avoid the race condition, the button should change the time to the time of the last message that was sent to the user on this node
(in other words, if this was an OS issue, it would crash)

Just a thought.

Replies are listed 'Best First'.
RE: Wrong behaviour in 'Newest Nodes'
by vroom (His Eminence) on Jul 21, 2000 at 22:46 UTC
    The time of the newest nodes page load is saved in a hidden field so when you update your flag it updates it to that time so it should be OK.

    vroom | Tim Vroom | vroom@cs.hope.edu
      Hmm guess i can sleep quietly now :)
      I got the feeling that its wrong since the time gets updated on the page ("Showing nodes created since Fri Jul 21 15:25")
      cheers!
RE: Wrong behaviour in 'Newest Nodes'
by Russ (Deacon) on Jul 21, 2000 at 23:01 UTC
    I just want to point out how much I really like the "I've Checked All These" behavior. It often works out that between the time I retrieved the last Newest Nodes page, and the time I have finished going to and from the posts listed there, there are more new nodes. (How's that for awful sentence construction?) So, the list changes to all my (once again) newest nodes when I click the button. This is extremely helpful.

    I haven't had a good opportunity to rave about the great forethought that went into this feature. As I recall, vroom added it on-the-fly in response to a thread a few of us were working on. He had added the feature before we were even finished discussing it.

    We've all seen the saying, "Fast, Correct, Cheap: Pick two." This time, we got all three. Once again, vroom, "You are the man."

    Russ
    Brainbench 'Most Valuable Professional' for Perl