I noticed that this method is not suited to provide data back from the server to a Netscape client.
You'll see that the method relies on the ability to change the document content, after it's fully loaded. I noticed that Navigator isn't too strong in these things.

However, supplying data from the Navigator client to the server is perfectly feasible.

As you know, the SRC attribute of the SCRIPT element allows for defining external script files.
This is exactly what we will do, on a certain event (a button click), we will reassign the SRC attribute. The trick is to dynamically generate the external script on the server, based on parameters the client provided.

The HTML page will contain at least two script blocks. One will be the container for the dynamically created script, the other will contain the managing code.

<script language="JavaScript" id="dynScript">
</script>

<script language="JavaScript">
function sendData(strData)
{
  dynScript.src = "dynScript.asp?" + strData;
}
  
function onDataReceived()
{
  alert("Data Received:" + strDataReceived);
}
</script>

As you see, the external script will be provided by dynScript.asp, that gets a parameter supplied (strData).
The server may use this parameter to do something client specific.

<%@language=JavaScript%>
<%Response.Expires = -1;%>
var strData;
strDataReceived = "User reported <%=Request.ServerVariables('QUERY_STRING')%>"
+ " at server time <=Date()>";
onDataReceived();

dynScript.asp has to return neat JavaScript (defined as language in the 'dynScript' script block remember).
In this sample, we will return a string that mentions both client as server data. At end of the dynamic script, we put a function that closely resembles an event handler.
The event handler (see client script) will show the received data in a message box. I'm sure you can come up with smarter things than this.