Confirmed users
753
edits
User:Automatedtester/FennecDriver: Difference between revisions
Jump to navigation
Jump to search
User:Automatedtester/FennecDriver (view source)
Revision as of 14:11, 27 September 2011
, 27 September 2011→Option 2
| Line 18: | Line 18: | ||
==Option 2== | ==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. | 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. | ||
The server part on the right of the image below would understand that JSON Wire Protocol meaning that we can give to the community and would get .NET, Java, Python and Ruby support straight away. | |||