sikuli-driver team mailing list archive

[RaiMan <question224126@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
you have 
- machine 1 having server s1 and client s1 (which are supposed to be some Sikuli scripts running from command line)
- machine 2 having server s2 and client s2 (which are supposed to be some Sikuli scripts running from command line)

the workflow:
c1 send 3 requests which are served by s2
c1 sends a request to s2, to signal machine 2 should take over (additional function f1 to be added on s2)
this function somehow wakes up c2
c2 starts sending requests to s1

In the easiest case, f1 can be the client c2, if c1 does not send
further requests to s2 (since it is blocked by running c2 now), until
maybe c2 sends a request to s1, to start from beginning or finish.

How to implement all this programmatically, depends on your needs and on
your scripting skills.

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