Why can't your desktop synchroninzation be used for AJAX?
Posted: Wed Apr 13, 2011 9:57 amWhy can't your desktop synchroninzation be used for AJAX?
aqt22 wrote:Why can't your desktop synchronization be used for AJAX?
Actually it can be, but for an AJAX application that is not the most effective method.
If you sync on the desktop that means that every few hundred milliseconds the eValid engine will interrogate the contents of the screen by grabbing a set of pixels and computing the checksup for that area. If the checksum matches, then the playback continues.
There's some overhead associated with this, maybe 1-2% of the CPU, but that's not the issue.
The real issues is that there is only one desktop, so if you have an eValid instance synching on the desktop you really can't have any other eValid instances also doing that.
Yes, we have a lock/unlock command to prevent unwanted conflicts, but you still don't have the parallelism that it would be great to have -- particularly if you are doing a loading run.
Instead, if you can sync on the internal contents of some DOM element property's value, then you can run any number of eValid in parallel, and the
overhead of doing any one sync is very low (< 0.1%).
eValid Support