Comment 7 for bug 778925

Of course will this be implemented event based on the Java level.

The polling loop above was just a quick and dirty solution to implement this with basic Jython features.
It can be smoothed a little, by putting a wait(1) before the next poll starts.

But somewhere inside will always be some polling loops. And the resulting cpu usage depends more on the number of parallel searches (which in turn are search loops with pauses (WaitScanRate)), then on the fact, that we are polling.

Beginning next week I will upload test versions.