DOM-based synchronization

Applying eValid to AJAX applications that require advanced DOM-based methods.

DOM-based synchronization

Postby TobyR » Mon Oct 31, 2011 5:19 pm

That DOM-based synchronization you have seems to be very powerful, but how often is it really used?
TobyR
 
Posts: 1
Joined: Mon Oct 31, 2011 2:42 pm

Re: DOM-based synchronization

Postby eValid » Thu Nov 03, 2011 12:39 pm

TobyR wrote:That DOM-based synchronization you have seems to be very powerful, but how often is it really used?
Good question and an excellent point. Indeed, it would be awful if there were too many of these!

As a rule of thumb, you probably will need one DOM-based synchronization step in your script for each separate AJAX-supported part of the web application. Once you have the AJAX part of the page loaded then you probably will not need to re-synchronize it. At least not until you take an action that fires up the AJAX push-pull communication.

In practical terms, thinking about scripts we've written on behalf of customers, you probably would be safe betting on one DOM-based sync for every 20-25 steps (commands) in your script.

In order words, in 4%-5% of your commands would be a good guess.

eValid Support
eValid
 
Posts: 2431
Joined: Tue Jan 01, 2008 12:48 pm
Location: USA


Return to AJAX Applications & DOM Processing

Design Downloaded from free phpBB templates | free website templates | Free Web Buttons