Table of Contents
Advertisement
•
is a comma-separated list of function names to be loaded from the
funcs
shared library. Function names are case-sensitive. You may use dash (-) in
place of underscore (_) in function names. There should be no spaces in the
function name list.
If the new SAFs require initialization, be sure that the initialization function is
included in the
funcs
For example, if you created a shared library
and
do_small_anim()
init_my_animations
Init fn=load-modules shlib=animations.so
funcs="do_small_anim,do_big_anim,init_my_animations"
If necessary, also add an
newly loaded plugin. For example, if you defined the function
init_my_new_SAF()
would a directive such as the following to
Init fn=init_my_animations maxAnimLoop=5
Instruct the Server to Call the SAFs
Next, add directives to
the appropriate time. The syntax for directives is:
Directive fn=function-name [name1="value1"]...[nameN="valueN"]
•
Directive is one of the server directives, such as
•
function-name is the name of the SAF to execute.
•
nameN
valueN
="
"
the SAF.
Depending on what your new SAF does, you might need to add just one directive
to
or you might need to add more than one directive to provide complete
obj.conf
instructions for invoking the new SAF.
list.
and also defines the initialization function
do_big_anim()
, you would add the following directive to load the plugin:
directive that calls the initialization function for the
Init
to perform an operation on the
to instruct the server to call each custom SAF at
obj.conf
are the names and values of parameters which are passed to
Creating and Using Custom SAFs
that defines two SAFs
animations.so
maxAnimLoop
:
magnus.conf
,
AuthTrans
Service
Chapter 4
Creating Custom SAFs
parameter, you
, and so on.
121
Advertisement
Table of Contents
