Question about the downside of using DOM

General discussion about eValid, its characteristis and applications.

Question about the downside of using DOM

Postby BillVV » Tue Mar 04, 2014 3:20 pm

Hello.

The capability that eValid has to manipulate the DOM seems pretty cool. But are there any downsides to this? Security, stability, reliability...that kind of thing.

Thanks
BillVV
 
Posts: 1
Joined: Tue Mar 04, 2014 3:14 pm

Re: Question about the downside of using DOM

Postby eValid » Wed Mar 05, 2014 11:45 am

BillVV wrote:Hello.

The capability that eValid has to manipulate the DOM seems pretty cool. But are there any downsides to this? Security, stability, reliability...that kind of thing.

Thanks


Hey BillVV. Thanks for asking!

Yes, there is a lot of power in eValid's DOM manipulation capability.

The eValid browser can do things a regular browser cannot do and should not do.

For example, it can completely fake a page (if you want it to). It is tricky to do, but basically you can replace the content of every DOM element in the page with different information...

You can even run your own JavaScript passages in eValid -- there is a special command for this.

But please remember, eValid is NOT intended to be used in the wrong hands: it is a test instrument intended for analysis purposes only.

One of the neatest things about eValid is that there is an available C++ interface.

Here is a summary of the features of the eValid Programmatic Interface [EPI] option:

http://www.e-Valid.com/Products/Documen ... mmary.html

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


Return to General Solution Topics

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