Re: OAS Session time out problem...

As taken from the manual regarding confirugation of the Web Parameters for your application:

Client Sessions

A pull-down menu to let the dispatcher know that the cartridge is session-enabled; requests originated from the same client receive the same cartridge instance. This is true as long as the idle time is less than the specified seconds in the Max session idle time field.

The possible values are:

Disabled - The cartridge is not session-enabled. This is the default. Enabled - The cartridge is session-enabled. If you select this option, you also need to enter a value for the Max session idle time field.

Max session idle time

Specifies the idle time (in seconds) for a cartridge that is session-enabled.

Once the idle time exceeds the time specified in this field, the cartridge instance is no longer associated with the request and can be bound to any other incoming request. After the instance expires, the client asking for the expired cartridge receives a page back indicating that the session expired. The subsequent request starts a whole new session.

Use the Max session idle time field with caution. If you set this field to a very large number, during that time, the cartridge is unavailable to any other request. The optimal value is dependent on the functionality of the cartridge. Set it to a value that is large enough to allow multiple requests within the session to complete, but small enough so that it is not stopping the cartridge from being used by other requests unnecessarily.

The default for this field is 0.

HTH. Finn

Dany Thivierge <dany.thivierge_at_cgi.ca> wrote in message news:pUcp5.437$nr5.10691_at_weber.videotron.net...
> Hey Thank Finn!
>
> Can you told me what to do to setup my cartridge to be "session
> enabled"???
> And what will be the impact of that thing over my application?
> I use Session parametrers and i dont want then to behave otherwise than
 they
> do now...
>
> Thank again for your help!
>
>
>
Received on Sat Aug 26 2000 - 12:34:01 CEST