| Yep, sounds like a pain. Even loading 500 "rows" of whatever in a static html file is going to be noticable, so it'll be slower in something dynamic. (ignoring that a visible refresh every 10s [even if it did return the user to the spot they were reading] sounds horribly annoying.)
As far as returning them to their current spot, that's even harder. How do we know where they're scrolled to? eg: They PGDN'ed several times and now "see" rows 150-164 on the screen. (obviously variable by screen size) You're looking to return them to row 150 to continue viewing with the possibility that there's new data below?
I'll let you know if I think of something, but it seems very awkward. Now if there were some form fields and the cursor was in one, it might be a bit easier.
-r |