Page 1 of 1

Why can't eValid drive HTTP protocol directly?

PostPosted: Mon Nov 21, 2011 6:10 pm
by cwillie
Why can't eValid drive HTTP protocol directly?

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

PostPosted: Mon Dec 05, 2011 9:30 am
by eValid
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