Now that we have our Selenium Standalone server up and running, it's time for us to create the RemoteWebDriver client. Fortunately, we don't have to do much to create a RemoteWebDriver client. It's nothing but the language-binding client libraries that serve as a RemoteWebDriver client. RemoteWebDriver will translate the test-script requests or commands to JSON payload and send them across to the RemoteWebDriver server using the JSON wire protocol.

When you execute your tests locally, the WebDriver client libraries talk to the Chrome Driver, IE Driver, or Gecko Driver directly. Now when you try to execute your tests remotely, the WebDriver client libraries talk to Selenium Standalone Server and the server talks to either the Chrome Driver, the IE Driver, or the Gecko Driver for Firefox requested by the test script, using the DesiredCapabilities class. We will explore the DesiredCapabilities class in the next section.