application, instance	A copy of scraper application executed somewhere.
worker	A piece of javascript code executed in separate thread in application.
application tag	a short string that corresponds to specified application
worker tag	a short string that corresponds to specified worker

The javascript source code may be located either locally (see command line) or in control panel

There is a special code called library. It can be located either in local file library.js or in control panel (with corresponding checkbox enabled).

The library code is executed once before every worker. For example:

Library:

	var x=2;
	sbcore.Print("Lib!");
	

Worker #1:

	sbcore.Print(++x);
	

Worker #2:

	sbcore.Print(x+5);
	

When executed, the output will be:

	Lib!
	3
	Lib!
	7
	

Actually, the output may be slightly different, because workers are executed in separate threads, and there is no way to learn the execution sequence. So, the output may look like this:

	Lib!
	Lib!
	7
	3
	

Of cause, the above library functionality might be achived in another way:

	sbcore.Include( "/path/to/lib.js" );
	... your code follows ...
	

Both workers and application has tags.

The general rule is: the application runs the worker with the same tag name.

There are special tags though:

ALL	Worker with ALL tag will run on all applications, except thouse with None tag. Application with ALL tag will run all workers, except thouse with None tag.
None	Worker with None tag will not be executed anywhere. Application with None tag will stay idle and will not execute anything.

Every application will request workers from server every 10 minutes.

If worker was modified in control panel, it will be automatically restarted on all corresponding devices.

New workers may be executed automatically when they are created.

This functionality does not work for workers executed from command line.

Functions

Variables

Samples

Command line