>>ActiveX is always client side
See, that shows you how awful I am. :)
Already looked... definitely not there. Hence, I asked here. :) Even without speaking Japanese you can get the gist of the site. ActiveX Object loads, displays index. If you click one of the next or previous page links, only the ActiveX object updates... the page doesn't reload. The guts of the page are summed up in a few Javascript() routines. It sets start to increment * page number, checks the form for any newly selected checkboxes, then runs the following.
function change(url)
{
document.getElementById('RESULT').innerHTML = '<br><br><br><br
+><br><br><br><center><img src="img/loading.gif"></center>';
Initialize();
if(req != null)
{
req.onreadystatechange = Process;
req.open("GET", url,true);
req.send(null);
};
}
// ------------------------------
// Initialize(ajax)
// ------------------------------
function Initialize()
{
try
{
req = new ActiveXObject("Msxml2.XMLHTTP");
}
catch(e)
{
try
{
req = new ActiveXObject("Microsoft.XMLHTTP");
}
catch(oc)
{
req = null;
}
}
if(!req && typeof XMLHttpRequest != "undefined")
{
req = new XMLHttpRequest();
}
};
There's a little more to it than that, but that's generally it. I guess the idea would be to open the same ActiveX object with a Perl Module that my browser is opening?