What's this about?
I had a site written in ASP.Net, every morning that I went to check it, it would take an age to start and then it would work great but after a while, if no-one used
it, the server would unload it.
This started to annoy me, so I did a "google" and it's a common problem, so I thought of a simple solution.
I have 3 other sites, they are quite popular and are written in HTML or the original ASP, so I added a hidden IFRAME to my ASP.Net site, so when someone browsed one of those sites, my site would be refreshed.
I can see a problem with that:
Yeah, so can we, if no one browses the sites then the Asp.Net site doesn't get started.
My solution:
Quite simple really, we need a central resource that links to all the sites to keep
them refreshed and that's what this site does.
The more sites that we can link together into this syndicate, the more sites we
can keep refreshed.
If my website includes the IFRAME to link to you and then you have an IFRAME linking to me, won't we get in to an ever decreasing loop?
We've thought of that, we check the Session ID, once we've displayed the IFRAMES once, we don't show them again if its the same Session ID so breaking the loop.