Please remember this is a work in progress. Home » Classes

Classes

 

TIWSessionOptions

 

Groups all session control specific properties. TIWServerController creates an instance of this class which is used internally.

Unit

IWServerControllerBase

Class hierarchy

TPersistent -> TIWSessionOptions

Methods

Create [Public]

Declaration: constructor Create(AServerControllerBase: TIWServerControllerBase);

Description: Constructs an instance of the class TIWSessionOptions and initializes its data.

Parameters:

  • AServerControllerBase (TIWServerControllerBase): [param description]

Assign [Public]

Declaration: procedure Assign(ASource: TPersistent); override;

Description: Copies properties values from another TIWSessionOptions instance or TPersistent descendant.

Parameters:

  • ASource (TPersistent): TIWSessionOptions instance to copy properties from

Properties

UniqueURL: Boolean; [Published, Read/Write]

When True, SessionID will be also included in the session URL. Each session has its own unique URL. Setting this property to True has the same effect of previous setting AllowMultipleUsersPerSession to True in previous IntraWeb versions.

SessionTimeout: Cardinal; [Published, Read/Write]

Use this property to indicate the amount of time (in minutes) a user session can remain idle (ie, no user activity in the browser) at the server side. Read only for Personal and Standard editions with the default value of 20 minutes.

Default value for IntraWeb Ultimate is 10 minutes

LockSessionTimeout: Cardinal; [Published, Read/Write]

this property represents the time IW will wait before rejecting a request for a locked session. This shouldn't happen in normal circumstances, but it is possible that the same session receives 2 requests which require session locking. So, imagine this scenario:

- Request 1 locks session "A"
- Session "A" starts processing request 1 and generating a new response
- Request 2 is received also requiring session "A"
- Session "A" can't be locked again, so request 2 is put on hold until request 1 is completed
- The wait time can be up to "LockSessionTimeout" milliseconds, i.e. after 30000 milliseconds, if Request 1 is not yet completed, IW server will respond to Request 2 with an error, so it will know that the server can't respond to that request at that time

Default value is 30000 milliseconds

AllowSearchEngines: Boolean; [Published, Read/Write]

When False, all requests coming from search engines and bots will be blocked (a response 404 - Not found will be generated) before creating a new session. Search engines and bots can generate hundreds or even thousands of requests which can put a web application under heavy load. If you don't require your application to be discovered by bots/search engines, leave this as False.

Default value is False

 

Terms of Use | Privacy Statement © 2002 - 2019 Atozed Software