| || |
Ajax Technology - Web Protocol or True Client Protocol to be used
I am having an Informatica product which has got components developed in Ajax technology. Is there a limitation in terms of using standard Web protocol for Ajax? Problem in using True Client protocol is the memory consumption and the number of Load Generators required to simulate more users.
I would appreciate, If I have a reply for this.
This is in the wrong Forum... but I will answer anyway.
The standard Web protocol can't handle AJAX... and trying to correlate it would drive you mad! This is the real reason TruClient was developed. It eliminates correlation... essentially by running a 'real' browser (IE or FF).
Yes TruClient does take more resources to run. But if you have a 'current' hardware platform you should be fine. You might not be able to run 200 users per generator, but with a quad core, 16gb ram, Windows 7 computer you can probably get to at least 100. The timesavings will more than cover the cost of the hardware.
Honestly I can't image ever going back to the HTTP/HTML protocol now that I have worked in TruClient for the past few years. TruClient is not perfect (yet ), but the timesavings, ability to modify scripts without re-recording, no correlation needed, are enough to make it my initial protocol I record with. I only revert back to HTTP/HTML mode if I absolutely have to.