Comments on: Dissecting Selenium WebDriver JSON WireProtocol http://www.roussev.org/2010/02/dissecting-selenium-webdriver-json-wireprotocol/ a Web Developer creating elegant aesthetic software Tue, 16 Feb 2010 09:25:10 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: atanas http://www.roussev.org/2010/02/dissecting-selenium-webdriver-json-wireprotocol/comment-page-1/#comment-1140 atanas Mon, 08 Feb 2010 20:24:16 +0000 http://www.roussev.org/?p=567#comment-1140 Out of curiosity, could you elaborate why didn't you use HTTP/JSON protocol for IE, but JNA was preferred? Out of curiosity, could you elaborate why didn’t you use HTTP/JSON protocol for IE, but JNA was preferred?

]]> By: Simon Stewart http://www.roussev.org/2010/02/dissecting-selenium-webdriver-json-wireprotocol/comment-page-1/#comment-1115 Simon Stewart Fri, 05 Feb 2010 12:49:28 +0000 http://www.roussev.org/?p=567#comment-1115 JNA (and, before that, JNI) is only used with the IE driver in webdriver. The HTTP requests are sent to Firefox (and any instance of webdriver which isn't running in the same process as your test) using the Jakarta HTTP Client as UTF-8 encoded JSON. If we wanted to, we could use an HttpConnection from the JDK, but the httpclient is used elsewhere and is far more robust. The reason for this design is that it allows us to support other languages (such as Ruby, Python and C#) with minimal effort. After all, almost every language has libraries for both HTTP and JSON :) JNA (and, before that, JNI) is only used with the IE driver in webdriver. The HTTP requests are sent to Firefox (and any instance of webdriver which isn’t running in the same process as your test) using the Jakarta HTTP Client as UTF-8 encoded JSON. If we wanted to, we could use an HttpConnection from the JDK, but the httpclient is used elsewhere and is far more robust.

The reason for this design is that it allows us to support other languages (such as Ruby, Python and C#) with minimal effort. After all, almost every language has libraries for both HTTP and JSON :)

]]>