Imbedded Interface Points (IIPs)
The Framework is shipped with a large number of imbedded interface points (IIPs).
IIPs are places at which externally exposed code is invoked to perform specific internal (or imbedded) logic while the Framework is executing.
For example, in Windows applications there is an IIP method named avConnectFiles that defines how files are to be connected up to a server system by the Framework.
This standard shipped IIP version does this:
Mthroutine avConnectFiles options(*Redefine)
* ==> Define_map *input #std_obj #UserProfile
* ==> Define_map *input #vf_elnum #DftBlockSize
* ==> Define_map *input #vf_elnum #DftMaxRecSel
USE BUILTIN(CONNECT_FILE) WITH_ARGS('*' *SSERVER_SSN #DftBlockSize.Value
#DftMaxRecSel.Value)
Endroutine
If you want you can modify this shipped IIP logic to do something different for your Framework.
In Windows applications the IIPs are defined as methods in the shipped component UF_SYSTM.
In Web browser applications the IIPs are defined as RDML functions in the shipped process UF_SYSBR.
If you want to learn more about IIPs then a good place to start is by looking at the source code shipped in component UF_SYSTM (for Windows applications) and in the functions contained in the process UF_SYSBR (for Web browser applications).