I think you should write a COM object that installs with the page... maybe a browser helper object.
Most users won't think twice before Clicking OK on the download dialog box it throws up so you don't have to worry about that "certificate" nonsense. Besides, it is expensive to do it that way.
So anyway, you convice your users to load your code onto their system. The code can call the Windows API to put itself to sleep for 5 minutes.
Then, when it wakes up, it can examine the IE windows and look for a ? in the querystring!
Another approach might be to do it all server side using ASP and MTS/COM+
The only purpose of the ASP page would be to pass the entire Request object off to a MTS package.
Inside the package, you do a database query that creates a huge cartesian product. It is best to do this either against a huge database that nobody else is using or you could get away with a smaller database if it is running on some pitiful old machine... Maybe a 233MHz PII with 64MB of
RAM.
Anyway, the point of the query is not to actually return any data, you want it to hang up.
The trick is you bump your transaction timeout up to 5 minutes on the package.
After it times out and control returns to your ASP page, the page does a Response.Redirect to itself forcing the browser to reload and try again.
The only reason I need this is because when I have a page that pulls information from the database, if you leave the page then go back to it with back button, it says the page needs to be refreshed.
Any other ideas about how to get round this appreciated...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.