Link to home
Start Free TrialLog in
Avatar of Titus57
Titus57

asked on

AJAX refresh pause question

I have developed a SCADA app that uses AJAX to ping my DB on a regular interval, which serves as a silent refresh on the page.  It works beautifully, with the one exception of when a user attempts to open a drop down menu.  Because the menus are located on the child page, the silent refresh kicks the user out of the menu when triggered.  Is there a way to freeze the refresh contingent upon the menu form being opened?  This is tricky because the refresh command is located on the parent page.  

Your help is most sincerely appreciated.
ASKER CERTIFIED SOLUTION
Avatar of Graham N.
Graham N.
Flag of United Arab Emirates image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Titus57
Titus57

ASKER

Okay, that makes sense... my particular solution is classic asp, so I'm not sure if the syntax would be the same.  Both parent and child frames have .asp extensions.  Do you have a suggestion for how I can make a callback to the parent with that layout?

I am not opposed to using an iFrame if it gets the job done, I just am not familiar enough with them to know if they can handle processing dynamic db content like asp can.
If the ASP pages are being rendered in HTML the syntax in terms of calling the parent frame would essentially be the same.

In other words:  parent.functionname()

Iframes would provide the same level of reliability and speed, but if you are not familiar with them better to avoid them as this could just end up creating a different set of problems for you!

It is a long time since I touched anything related to SCADA - but it used to rely heavily on HTML rendering hence my original suggestion.
Avatar of Titus57

ASKER

I actually didn't wind up using this solution but it is viable.  I ended up blowing up the entire process and reworking the AJAX to conditionally refresh only when prompted and stop after a fresh timestamp was seen in the db, thus eliminating the need for the pause... a much less data/processor intensive solution with nearly identical results