[
https://issues.apache.org/jira/browse/NUTCH-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14355926#comment-14355926
]
Lewis John McGibbney commented on NUTCH-1948:
---------------------------------------------
bq. Would something like
https://github.com/xautlx/nutch-ajax/issues/2#issuecomment-77892177 be useful?
Makes perfect sense yes. It certainly would be useful. It was obvious that
there would, over time, be suggestions to improve the selenium plugin. I am
glad to that we are able to identify some already.
> Make the Selenium remote web driver specification, configuration and
> selection available via a Factory-type mechanism
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: NUTCH-1948
> URL: https://issues.apache.org/jira/browse/NUTCH-1948
> Project: Nutch
> Issue Type: Improvement
> Components: plugin, protocol
> Affects Versions: 1.10
> Reporter: Lewis John McGibbney
> Fix For: 1.11
>
>
> Right now we only use the FirefoxDriver, however we could also use the
> following
> * ChromeDriver
> <https://selenium.googlecode.com/git/docs/api/java/org/openqa/selenium/chrome/ChromeDriver.html>,
>
> * FirefoxDriver
> <https://selenium.googlecode.com/git/docs/api/java/org/openqa/selenium/firefox/FirefoxDriver.html>,
>
> * InternetExplorerDriver
> <https://selenium.googlecode.com/git/docs/api/java/org/openqa/selenium/ie/InternetExplorerDriver.html>,
> and
> * SafariDriver
> <https://selenium.googlecode.com/git/docs/api/java/org/openqa/selenium/safari/SafariDriver.html>
>
> They could be available via a Factory-type mechanism which would allow us to
> define the driver within nutch-site.xml even.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
