mercer8 wrote:We're considering eValid vs. a product that uses HTTP/S simulation and we're wondering if you could give us a succinct description of why eValid is better?
They do the same thing, don't they?
Mercer
Good question. We'll try to make it short and sweet.
No, not the same.
The eValid browser is fully stateful -- it remembers internal states -- but as you may recall, HTTP/S protocol is "stateless", no memory.
The difference is an important one: the full-broswer approach gives you 100% realism in terms of the interaction between the [simulated] user and the web application.
By comparison, the HTTP/S protocol approach only simulates the traffic
between the server and the client (the client browser).
If you don't need to have the traffic vary as the state of the browser changes as the result of user actions, then you don't need eValid. But most users DO want that realism.
-The eValid Support Team
