Under normal cicumstances that would always refresh the page on which the link is clicked, which isn't really ideal. What you really want is to mimic normal browser behaviour but with server-side flexibility and control.

but it occurs to me that this could be a good solution if combined with a very small, preferably blank, routing frame. All links should be target="trampoline" and the very small, quick page returned to the trampoline frame could force the selected content frame to refresh.

but op would still be using two or more cgi calls, as well as the javascript, where one at most should do it. it's going to be slow and ungainly and have way too many points of possible failure.

/will can't remember the last time frames seemed like a good idea, but thinks netscape 2 was still a novelty at the time...