User:Automatedtester/FennecDriver: Difference between revisions

Jump to navigation Jump to search
Line 16: Line 16:
==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
[[File:Option2or3.jpg]]
[[File:Option2or3.png]]


==Option 3==
==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+
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+
Confirmed users
753

edits

Navigation menu