sikuli-driver team mailing list archive

[RaiMan <question268694@xxxxxxxxxxxxxxxxxxxxx>]

Question #268694 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/268694

    Status: Needs information => Answered

RaiMan proposed the following answer:
ok, I do not have an easy solution for that - or to be honest: not any
working solution at all.

The basic problem with Grid2:
By design, you do not know, on what machine(s) your remote web driver request(s) execute, since this is decided by the hub based on the given desired capabilities.
So even if you have a Sikulix RunServer (possible with 1.1.0) running on the node machines, you do not know to which node machine to send your Sikulix run request, without replicating the hub's node selection logic, which in turn does not make any sense.

Since the run requests sent to the SikuliX RunServer themselves use HTTP REST, one might use Webdriver's exec feature to inject a JavaScript snippet, that in turn issues an adequate  run request now locally on the node machine to the local Sikuli RunServer.
If you would decide to use JavaScript for your SikuliX remote snippets, this solution would be very lean and fast.

That this principally works, you can see here:
http://www.sikulix.com/support.html

Be sure to use the latest nightly build of version 1.1.0.

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.