Re^5: refreshing a page/session without re-submitting search

"refresh" is the wrong term. The page isn't reloaded, the javascript code simply re-writes that part of the HTML. In your case, you don't need to have the javascript update the ... part of the page since the data is already there at the bottom of the page like you found. If you want the hit count, don't look in

<span id="hitCount_top">...</span> results found
[download]

look at the numHits javascript at the bottom of the page.

Are you trying to re-display the results exactly as they are when you look at it in a browser or are you parsing the file to get bits of information about the result set?

Comment on Re^5: refreshing a page/session without re-submitting search Select or Download Code

Replies are listed 'Best First'.
Re^6: refreshing a page/session without re-submitting search by seaver (Pilgrim) on Sep 23, 2004 at 15:58 UTC
OK I starting to understand this now, thank you What's happening is that the hitcount itself goes up as the server continues to search, so I can see now that the JavaScript simply waits a little while, and then writes in the hitcount. But from what you say, the final hitcount is already found and present in the bottom of the page am I right? What I'm trying to do here is to make sure I get ALL the results available, because I want to go on to another page, and click the email button, but I thought I wasn't getting ALL the results available first (whether or not they are on the same page). I'm expecting 600, as determined by my web search but only getting 67, and it occured to me this morning that the Http::Request::Form which automatically does the hidden buttons and defaulted values may be missing something which causes the search to be limited, so checking it out thanks for your help Sam	[reply]

Replies are listed 'Best First'.

Re^6: refreshing a page/session without re-submitting search
by seaver (Pilgrim) on Sep 23, 2004 at 15:58 UTC

What's happening is that the hitcount itself goes up as the server continues to search, so I can see now that the JavaScript simply waits a little while, and then writes in the hitcount.

But from what you say, the final hitcount is already found and present in the bottom of the page am I right?

What I'm trying to do here is to make sure I get ALL the results available, because I want to go on to another page, and click the email button, but I thought I wasn't getting ALL the results available first (whether or not they are on the same page).

I'm expecting 600, as determined by my web search but only getting 67, and it occured to me this morning that the Http::Request::Form which automatically does the hidden buttons and defaulted values may be missing something which causes the search to be limited, so checking it out

thanks for your help
Sam

[reply]