Using preemptive web processes
The 4D Web Server allows you to take full advantage of multi-core computers by using preemptive web processes in your applications. You can configure your web-related code, including 4D tags, web database methods or ORDA REST class functions to run simultaneously on as many cores as possible.
For in-depth information on preemptive process in 4D, please refer to the Preemptive 4D processes section in the 4D Language Reference.
Availability of preemptive mode for web processes
The following table indicates whether the preemptive mode is used or is available, depending on the execution context:
|4D Server||Interpreted (debugger attached)||Interpreted (debugger detached)||Compiled|
|Web Server||cooperative||web setting||web setting|
|Web Services Server||cooperative||web setting||web setting|
|Web Server||cooperative||web setting|
|Web Services Server||cooperative||web setting|
- REST Server: handles ORDA data model class functions
- Web Server: handles web templates, 4DACTION and database methods
- Web Service Server: handles SOAP requests
- web setting means that the preemptive mode depends on a setting value:
- when Scalable sessions option is selected, the preemptive mode is automatically used for web processes.
- otherwise, the Use preemptive processes option is taken into account.
- regarding Web service processes (server or client), preemptive mode is supported at method level. You just have to select "Can be run in preemptive processes" property for published SOAP server methods (see Publishing a Web Service with 4D) or proxy client methods (see Subscribing to a Web Service in 4D) and make sure they are confirmed thread-safe by the compiler.
Writing thread-safe web server code
All 4D code executed by the web server must be thread-safe if you want your web processes to be run in preemptive mode. When the preemptive mode is enabled, the following parts of the application will be automatically evaluated by the 4D compiler:
All web-related database methods:
compiler_webproject method (regardless of its actual "Execution mode" property);
Basically any code processed by the
PROCESS 4D TAGScommand in the web context, for example through .shtml pages
Any project method with the "Available through 4D tags and URLS (
4DACTION, etc.)" attribute
Triggers for tables with "Expose as REST resource" attribute
ORDA data model class functions called via REST
For each of these methods and code parts, the compiler will check if the thread-safety rules are respected, and will return errors in case of issues. For more information about thread-safety rules, please refer to the Writing a thread-safe method paragraph in the Processes chapter of the 4D Language Reference manual.
Thread-safety of 4D web code
Most of the web-related 4D commands and functions, database methods and URLs are thread-safe and can be used in preemptive mode.
4D commands and database methods
All 4D web-related commands are thread-safe, i.e.:
- all commands from the Web Server theme,
- all commands from the HTTP Client theme.
The web-related database methods are thread-safe and can be used in preemptive mode (see above):
On Web Authentication,
On Web Connection,
On REST Authentication...).
Of course, the code executed by these methods must also be thread-safe.
Web Server URLs
The following 4D Web Server URLs are thread-safe and can be used in preemptive mode:
- 4daction/ (the called project method must also be thread-safe)
- 4dcgi/ (the called database methods must also be thread-safe)
- 4dimgfield/ (generated by
PROCESS 4D TAGSfor web request on picture fields)
- 4dimg/ (generated by
PROCESS 4D TAGSfor web request on picture variables)
Preemptive web process icon
Both the Runtime Explorer and the 4D Server administration window display a specific icon for preemptive web processes:
|Preemptive web method|