NightWind's Card Searcher

It seems this is one of the (many) problems with an ASP server... I've seen this stuff happen before with the other projects I'm working on - even those which had existing code I'm working off.

I can see the Gloopzilla bug and here's why:

Thing is, the search page "goes cold" if it isn't accessed every now and then. And when that happens, the code doesn't complete it's full run - which means you get Gloopzilla €results. The part which takes the longest to execute is where it obtains the HS feed. On slow startup it will time out, thus fooling the rest of the code to print Gloopzilla's quantity instead.

This explains why the Khrimech problem reported by Zerosa was only seen by him the first time he ran it. When I ran it, it was perhaps during a busier time, when the page was already warmed up. Same goes for Nacho's results. I saw the Gloopzilla bug when I ran it during the quiet hours, but upon refreshing the results in the next minute or so, the bug "disappeared".

If the stats from the other finance projects serve right all ASP pages should need to be accessed every 20 mins to keep them warm.

This also means that most users won't see the Gloopzilla bug because there are enough users to keep the page warm during busy hours. This will however, cause the bug to appear to the users who use the page during the quiet hours.

First workaround:
To have a javascript page on a 24/7 that constantly requests a dummy search every 20 mins to keep the page warm - But this doesn't work as I don't have access to a machine which can run a javascript page and be kept on 24/7.

Second workaround:
Refresh the page if you see the Gloopzilla bug. After refreshing, you should be then seeing the "warmed up" and thus correct results. If that still doesn't work, try running the search after a 5 min wait.

This bug should only impact the HS results and not the personal store results. If you're on low bandwidth, I'm sure you'll notice that wikipedia on first load takes about 5 times as long to even show the background image.

All, if you see the Gloopzilla bug, let me know how many refreshes and the duration it takes for the bug to disappear. Does an immeadiate refresh work? 2 refreshes? Or do you have to wait 5 mins? I'm going to do some testing of my own, but it's hard as the environment can't be isolated.

Also, tell me what you think of the workarounds above. If you are annoyed by the "Gloopzilla" bug which shows 17 for all the other cards, I can remove the HS results altogether.