Hello folks,
I have some serious problem with my application.
Well, the thing is that
my client wants an application that runs 24/7,
every single day from January 1st all the way through 31st December,
every night and day without stopping!
And so...
I tried this and that
but came to a conclusion that loading each application through
an IFrame would be the best way to do that!
And it's like this,
there's a main application, which is embedded in a html
and has all the logic about handling the IFrame and loading
sub-applications on a regular basis, through a timer..
and each application is being loaded like a slideshow and disappears
and another page with another application is set as the source
for the same iframe and therefore next slide, next slide etc..
So basically, there seems to be no problem related with the memory
usage or something..
Yet what happens is that
after about 3 days of running,
it throws an abnormal error related with bitmap processing,
something like 2015 error, which wouldn't normally be thrown.
So I event put try{ } catch{e:*} stuffs in every possible place
and yeah it works
but what happens is that my application somewhat slows down...
(How could it slow down when a new page is actually set as the
source for the IFrame?!!)
To be frank, I have no idea what in the world is wrong...
One thing that's really getting on my nerves is that
it's being run on Windows 2003 Server. Could it be a problem???
Also, I even made another timer in the main application which gets
reset and starts when each sub-application is loaded. And it
triggers a
function to load next slide when no response comes back from the
sub-application to the main one event after 10 minutes.(they
communicate
through LocalConnection objects). So I thought this would be a
perfect way to make a nonstop application but it just slows down...
which drives me somewhat crazy...
Any ideas???
