Confirmed users
753
edits
User:Automatedtester/FennecDriver: Difference between revisions
Jump to navigation
Jump to search
User:Automatedtester/FennecDriver (view source)
Revision as of 13:58, 27 September 2011
, 27 September 2011→Option 1
| Line 13: | Line 13: | ||
Server Architecture The server is going to be a Jetty Server on the device with servlets to handle the different commands available in the JSON Wire Protocol. This approach also means that we can use the Selenium Grid to parallelise since devices can be added and the central hub would understand and forward the commands to this server. | Server Architecture The server is going to be a Jetty Server on the device with servlets to handle the different commands available in the JSON Wire Protocol. This approach also means that we can use the Selenium Grid to parallelise since devices can be added and the central hub would understand and forward the commands to this server. | ||
[[File:option1.png]] | [[File:option1.png]] | ||
==Option 2== | |||
The next option would be to create a lightweight XPI that would do XmlHttpRequest to the Server on the client side asking for the next available command. This would invert the Client/Server approach that is currently in Selenium WebDriver.This approach would mean that we can keep the XPI lightweight and keep the device's memory footprint really small and not have a jetty service running | |||
==Option 3== | |||
This option is similar to Option 2 except that it would use websockets instead of XMLHttpRequests. Unfortunately this approach would not give use backwards compatibility if the code was ported to work on Desktop Firefox. Currently the Selenium project supports Firefox 3+ | |||