1 $group
2 $
3 var sect = {
4 title: 'The "runnerServer"'
5 };
6 section( §)
7 p When the Wizzi factory is used in a server application,
8 \b or in a long running process where many jobs are
9 \b executed, it is useful to access factory
10 \b services, prepared at startup, directly from the
11 \b JsWizzi code inside ITTF documents.
12 p There are two JsWizzi global functions for this
13 \b purpose.
14 ul
15 li $.api( functionName, ... arguments ... )
16 p Allow to call a user function declared on start up.
17 li $.loadModel( modelName )
18 p Allow the retrieval of a Wizzi Model preloaded on start up.
19 h3 The wizzifile.js
20 p ... TODO ...
21 h4 Event handler wizzifile.onConfig( config )
22 p This event is raised before creating the runnerServer instance.
23 \b At this point we can call the config.get(propertyName) and
24 \b config.set(propertyName, value) methods on the config object.
25 h4 Event handler wizzifile.onStart( runnerServerInstance, config )
26 p This event is raised before the initialization of the wizzi factory
27 \b contained in the runner server. At this point we can call the
28 \b runnerServerInstance.registerApi(name, function) method, the
29 \b runnerServerInstance.registerPlugin(pluginNameOrPath) method
30 \b and the runnerServerInstance.registerGlobalContext(object) method.
31 h4 Event handler wizzifile.onPrepare( runnerServerInstance, config )
32 p This event is raised when the wizzi factory contained in the runner server
33 \b has benn initialized. Now it is forbidden to call the
34 \b registerPlugin and registerGlobalContext methods but we
35 \b can call the runnerServerInstance.loadModel and
36 \b runnerServerInstance.transformModel methods.