ConfigureAWPContext (Function)

WINDEV, WEBDEV AND WINDEV MOBILE
ONLINE HELP

Version:

Home | Sign in | English

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

ConfigureAWPContext (Function)

In french: ConfigureContexteAWP

Configures the operating mode of AWP context.

See Managing AWP contexts for more details.

Remark: If ConfigureAWPContext is not called, the default management mode of contexts is the management of contexts via cookies.

Caution: This function requires a good knowledge of WEBDEV.

Example

// Manage the context of a file on the server
// and transmit the identifier by cookie
ConfigureAWPContext(ctxDisk, ctxIDCookie)

Syntax

ConfigureAWPContext(<Content storage mode> [, <Identifier transmission mode>])

<Content storage mode>: Integer constant

Mode for storing the content of context:
ctxCookie The content is transmitted in a cookie (behavior compatible with version 11).
Caution: This constant must not be used to store sensitive data. Indeed, this information is stored "without being encrypted".
ctxDisk The content of context is saved in a file on the server.

<Identifier transmission mode>: Integer constant (optional)

Define the transmission mode of identifier (taken into account only if <Content storage mode> corresponds to the ctxDisk constant):
ctxIDCookieURL
(default value) The identifier is transmitted by cookies. If the cookies do not operate, the identifier is transmitted by the URL. When creating the context, the two modes are used because it is not possible to know whether the cookies will be accepted or not.
ctxIDCookie The identifier is transmitted by a cookie.
ctxIDUrl The identifier is transmitted by the URL.

Remarks

We recommend that you use ConfigureAWPContext in the event "Initializing" of the project. Indeed, this mode cannot be modified once the session was started.
ConfigureAWPContext is taken into account in AWP mode only.
If ConfigureAWPContext is not called, the default management mode of contexts is the management of contexts via cookies.
Reminder: The initialization process of project is run whenever an AWP page is displayed.
Versions 20 and later
If your project uses pre-launched sessions, this function must not be used in the event "Initializing" of the project. This function must be used in the event "Initializing the project after connection to the site".
New in version 20
If your project uses pre-launched sessions, this function must not be used in the event "Initializing" of the project. This function must be used in the event "Initializing the project after connection to the site".
If your project uses pre-launched sessions, this function must not be used in the event "Initializing" of the project. This function must be used in the event "Initializing the project after connection to the site".
See The dynamic AWP pages for more details.

Component : wd250page.dll