INAE, but could you not persist the connection, sleeping in between batches and wrapping each batch in a table.
Does a mostly sleeping, persistant connection unduly tax Apache?
Don't most (many, all) browsers render a table as soon as it's complete?
The format of the links wouldn't have to change. Just put <table><tr><td> at the top of each batch and close it at the bottom, before sleeping for a few seconds then looping back to do the next batch.
...heading back to Barcelona.
Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon
| [reply]
[d/l] |
ambrus,
How do you think that could be implemented?
Given that I am not a devil - I have no idea how it would happen under the covers. I also wasn't too biased on the outside interface. You do bring up a good point:
as many people would just keep clicking Next until the whole database is searched
Again, I do not care how the functionality is acheived - even if it is nothing more than "add these node ids to my scratch pad/personal nodelet". I Just have found myself searching multiple times after discovering something I thought was not-important was later important.
So - if there is a way to achieve this functionality without the potential resource abuse - I would like to see it added.
| [reply] |
as many people would just keep clicking Next until the whole database is searched and only look at the results after that
I don't think that would be an issue. If the the default was for the articles to be unchecked and there was no select all mechanism, then you'd have to manually check all the ones you wanted to keep visible during your search.
--
"A long habit of not thinking a thing wrong, gives it a superficial appearance of being right." -- Thomas Paine
naChoZ
| [reply] |
