4.10.4Object InputVarBinder

Binder retreiving values from Nest input variables.

Object InputVarBinder

This binder initialize the variable with a pre-filtered input variable.

Nest system reads the input variables with the following priority:

- POST HTTP fields

but web application can define new Nest.filter functions to create new strategies to read the input variables, removing some of them, adding some of them and so on.

If a variable is defined in a higher priority input source, values eventually defined in lower priority sources are ignored.

Nest can optionally pass the input variables to an application-defined filter prior passing them too the modules. This helps the applicaiton to perform extra security checks or inject special variables autonomously.

Session variables are handled separately, and they are not usually served as input variables unless

If the service has an instance value, then the variable serched among the input elements is prefixed with a "_" string, where is the name of the service instance.

For example, in the following service:

   class Test(i) from Service(i)
      var = ServiceVar( InputBinder )

var will assume the value of the input variable named "var", if present. If the service is created with an instance name, for example "mytest", then the variable searched will be "mytest_var".

If the variable is not found in the Nest.input dictionary, the ServiceVar.value property will be nil, and the value of ServiceVar.isSet will be false.

See also: SessionBinder.

Made with http://www.falconpl.org