Most Selenium solutions involve running the Selenium RC Server JAR file (eg java -jar selenium-server-standalone-2.25.0.jar), letting that listen on port 4444, and then sending commands to it over a TCP connection. This is what clients like soda do. This project is slighly different. Instead, it uses the same Selenium JAR file, but it loads it in-process using the robust node-java bridge. In effect, this creates "JS bindings" to Selenium based on the Java interface. So we can now do advanced stuff with Selenium without having to convert the entire project to Java.