|
|
|
|
|
|
|
|
|
|
- Overview
- Importance of pre-launched sessions
- Principle of a request for displaying an Active WEBDEV Page
- Benefit of pre-launched sessions
- Implementation
- Steps to follow
- Enable management of pre-launched sessions
- Correcting errors specific to pre-launched sessions
- Webservices: "Recycling a pre-launched session" event
- Enabling pre-launched sessions on the server
A pre-launched session is a Web site (or Web service) session launched automatically on the Web server from the WEBDEV Application Server. The use of pre-launched sessions speeds up page display by anticipating time-consuming processes such as database connections and page configuration loading. Pre-launched sessions can be used with: - WEBDEV sites in Session mode,
- WEBDEV AWP sites,
- SOAP web services and REST web services.
 Novedad versión 2025For web services, it is also possible to use "pre-launched session recycling".
This operating mode is identical in any case. Note Pre-launched sessions are only allowed on the unlimited server or 10 connections. They are not enabled on the development computer. Importance of pre-launched sessions Principle of a request for displaying an Active WEBDEV Page To understand the importance of pre-launched sessions (especially for Active WEBDEV Pages), let's take a look at the principle of Active WEBDEV Pages. When a Web user performs a request from an Active WEBDEV Page, the following operations are performed: - The request is transmitted from the browser to the Web server.
- The Web server studies the request.
- The Web server transmits the request to the WEBDEV Application Server.
- The WEBDEV Application Server:
- loads the project corresponding to the page.
- runs the project initialization code, then the page code.
- returns the response to the Web server.
- The Web server returns the response to the browser.
Benefit of pre-launched sessions When displaying an Active WEBDEV Page, each call to the WEBDEV Application Server is entirely independent. Consequence Every time a request is made (and therefore every time a page is changed or an Ajax call is made), the WEBDEV Application Server reloads the project and re-executes the initialization code. The project initialization code often runs "long" operations: - connecting to the database,
- loading configuration files,
- ...
The pre-launched sessions ask the WEBDEV Application Server to perform these operations in advance. Therefore, when the request of the Web user reaches the WEBDEV Application Server, the application server only has to run the request and to return the result. Using pre-launched sessions results in shorter response times, since part of the code is executed in advance. However, pre-launched sessions do not reduce server load (the code is still executed) and do not replace the optimization of initialization code. Novedad versión 2025Additional option for web services: In the case of web services, an additional option can be activated: recycling of pre-launched sessions. If this option is enabled: - At the end of the web service call, the WEBDEV Application Server does not terminate the pre-started session associated with it.
- The "Recycle a pre-launched session" event associated with the project is then executed. This event can, for example, reset variables or connections specific to the client that called the web service.
- WEBDEV Application Server resumes waiting for connection to the web service (in pre-launched session mode).
Enable management of pre-launched sessions To activate the management of pre-launched sessions: - Display the description of the project configuration (of your site or web service):
- In the "Project Explorer" pane, select the desired configuration.
- From the context menu, select "Description".
- On the "Options" tab, check "Activar sesiones preiniciadas en el servidor de aplicaciones".
Novedad versión 2025For a web serviceit is also possible to activate connection recycling by checking the "Reciclar sesiones preiniciadas" option. This option offers the following benefits: - Reduced server resources: no need to create a session for each request.
- Database optimization: a single connection is maintained instead of a new connection for each call.
- Faster: the web service response is generated much more quickly.
- Validate. The project is recompiled.
To manage pre-launched sessions, several events are associated with the project: - "Initialization", a project event run before the request reaches the WEBDEV Application Server. This code is run when starting the pre-launched session.
- initialization in pre-launched session mode, executed when the WEBDEV Application Server processes the request.
Novedad versión 2025the "Pre-launched session recycling" event, if session recycling has been requested for the web service configuration.
If your project configuration uses pre-launched sessions, certain functions can no longer be used in the project initialization code. The corresponding errors are displayed in the "Compilation error" pane.
Reminder: To display the "Compilation errors" pane, under the "Inicio" pane, in the "Entorno" group, pull down "Paneles" and select "Panes" then "Compilation errors". Correcting errors specific to pre-launched sessions The errors of pre-launched sessions indicate which WLanguage functions are not allowed in the "Initialization" project event. To correct errors specific to pre-launched sessions, simply move the corresponding code to the "Initialization when connecting to a pre-launched session" event. When the site or web service is compatible with the pre-launched session mechanism, it can be deployed and pre-launched sessions activated on the WEBDEV Application Server. The list of functions not to be used in project initialization code is as follows:
| | | ASPDisplay | Llama a un script ASP externo y devuelve la página de resultados en la ventana actual del navegador. | | BrowserIPAddress | Returns the IP address of the client computer connected to the WEBDEV website. | | BrowserName | Returns the name of the browser of the Web user ("user agent"). | | BrowserPlatform | Returns the user's browser platform. | | BrowserType | Devuelve el tipo de navegador utilizado por el usuario de la Web. | | BrowserVersion | Devuelve la versión del navegador utilizado por el usuario de la Web. | | CancelarAWPContext | Borra del contexto AWP una variable añadida por DeclareAWPContext. | | CancelWebserviceContext | Deletes from the web service context a variable added by DeclareWebserviceContext. | | CertificateClientInfo | Returns information about the certificate used by the client computer. | | ConfigureAWPContext | Configura el modo de funcionamiento del contexto AWP. | | Confirm | Displays a message in a standard dialog box that proposes "Yes", "No", "Cancel" and returns the user's choice. | | ContextClose | Closes a page context. | | ContextOpen | Abre un nuevo contexto de página sin devolver la información al navegador. | | CookieRead | Retrieves the value of a cookie saved on the computer of Web user. | | DeclareAWPContext | Se utiliza para declarar una lista de variables cuyos valores serán persistentes entre sucesivas visualizaciones de Páginas WEBDEV Activas. | | DeclareWebserviceContext | Used to declare a list of variables whose value will be persistent between the successive calls to a web service. | | ExecuteDelayedProcedure | Ejecuta un procedimiento retardado (en el WEBDEV Application Server). | | FileDisplay | Displays a file in the user's browser. | | FramesetDisplay | Displays a WEBDEV frameset in the user's browser. | | FramesetRefresh | Refreshes a frameset displayed in the user's browser from the context on the server. | | FramesetUse | Displays a WEBDEV frameset in the user's browser and closes all the current page and frameset contexts. | | FreeAWPContext | Libera el contexto AWP por adelantado (en disco) para permitir que la otra llamada en el mismo contexto AWP se procese en paralelo. | | GglConnect | Manages authentication on a Google server (via the "OAuth 2.0" authentication mode). | | gpwOpen | Abre la ventana o página de inicio de sesión del Groupware Usuario. | | IdentifierAWPContext | Devuelve el identificador del contexto AWP. | | ImageArea | Devuelve el número del área de imagen en la que ha hecho clic el usuario de la Web. | | ImageXPos | Returns the horizontal position (X) of the mouse cursor in relation to the specified Image control. | | ImageYPos | Returns the vertical position (Y) of the mouse cursor in relation to the specified Clickable Image control. | | OKCancel | Displays a message in a standard dialog box that proposes "OK" and "Cancel" and returns the user's choice. | | PageCloseDialog | Cierra la página actual. Esta página fue abierta por PageDisplayDialog. Se puede devolver un valor de retorno a la página de llamada. | | PageDisplay | Muestra una página web en el navegador del usuario. | | PageDisplayDialog | Displays a page in modal mode. This function is used to establish a dialog with the user. The page is displayed in the foreground while the opening page is displayed in the background, grayed by the DDW mechanism. | | PageParameter | Returns the value of a parameter passed to the current page. | | PageRefresh | Refreshes a page displayed in the user's browser from the context on the server. | | PageUse | Muestra una página WEBDEV en el navegador del usuario y cierra todos los contextos de página actualmente abiertos en el servidor. | | PHPDisplay | Llama a un script PHP externo y devuelve la página de resultados en la ventana actual del navegador. | | rssDisplay | Builds a RSS feed and returns the content of the RSS feed to the client. | | ScriptDisplay | Calls an external script or page (.php, .asp, .mhtml or.mht) and returns the result page in the current browser window. | | StringDisplay | Devuelve una cadena específica (o un buffer) al navegador del cliente en respuesta a una petición. | | UploadCopyFile | Guarda un archivo "subido" por el usuario al servidor. | | UploadFileName | Returns the name of a file "uploaded" by the Web user. This file must have been uploaded: - via an "Upload" edit control.
- via a single-file or multi-file Upload field.
| | WebserviceClientIPAddress | Returns the IP address of the computer using and calling the web service. | | YesNo | Muestra un mensaje en un cuadro de diálogo estándar que propone la opciones "Sí" y "No", y devuelve la respuesta del usuario. |
Novedad versión 2025Webservices: "Recycling a pre-launched session" event In the "Recycling a pre-launched session" event, it is essential to reset all global variables that were initialized in the "Initialization when connecting to a pre-launched session" event. For example, if the customer's IP address is stored in a variable during a call, this variable must be emptied when the call is recycled. For example:
gsAdresseIP = WebserviceClientIPAddress()
gsAdresseIP = ""
Enabling pre-launched sessions on the server To activate pre-launched sessions for a site or web service: - Start the WEBDEV administrator.
- Go to the "Configuration" tab.
- Check "Permitir sesiones preiniciadas.". By default, all the sites and web services have 0 pre-launched sessions.
- Select the site or web service to be configured ("Sites" tab or "Webservices" tab).
- In the site parameters ("Parameters" option in the "Sites" tab) or Webservice parameters ("Parameters" option in the "Webservices" tab), specify the maximum number of pre-launched sessions to be used.
- Validate.
Remarks: - Pre-launched sessions are counted in the total number of connections to the site (or to the web service). This information must be taken into account when configuring the WEBDEV Application Server.
- The number of pre-launched sessions to be defined depends on the server usage and the number of requests.
- When a user logs in (sites in Session mode) or displays a page (AWP sites), the WEBDEV Application Server uses a pre-launched session of this application, if any. Otherwise, the WEBDEV Application Server launches a normal session, as if the site didn't have any pre-launched sessions.
- The number of available pre-launched sessions is checked every second, per site. Therefore, the number of pre-launched sessions depends on the number of connections (Session mode) or the number of times a page is displayed (AWP sites) per second.
- If a session takes longer than one second to (pre)launch, the number of pre-launched sessions actually available decreases.
Novedad versión 2025Webservices with session recycling: - session retraining is not carried out in the following cases:
- a WLanguage error in the code.
- thread (or parallel task) active after the response has been sent.
- use of the EndProgram function.
- sessions can be recycled a maximum of 200 times. Beyond that, the usual system of pre-launched sessions is used.
- the InRecycleMode function lets you know whether the code currently being executed has been executed since the "Recycle pre-launched session" event.
Esta página también está disponible para…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|