Why can't eValid drive HTTP protocol directly?

Use and application of the eValid server loading (LoadTest) capability. And in the cloud computing context for monitoring and loading.

Why can't eValid drive HTTP protocol directly?

Postby cwillie » Mon Nov 21, 2011 6:10 pm

Why can't eValid drive HTTP protocol directly?
cwillie
 
Posts: 1
Joined: Mon Nov 21, 2011 4:06 pm

Re: Why can't eValid drive HTTP protocol directly?

Postby eValid » Mon Dec 05, 2011 9:30 am

cwillie wrote:Why can't eValid drive HTTP protocol directly?
The quick answer here is, it doesn't need to.

However, eValid actions DO cause the browser to initiate and handle HTTP traffic to and from the browser. So the answer is that yes, eValid can [and does} generate HTTP traffic, it just does not do it from a direct port into the HTTP protocol.

This feature of eValid makes handling navigating to a page trivial: All eValid has to do is "get the URL" and the browser takes care of all of the heavy lifting.

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


Return to Performance/Load Testing

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