BSP application processing uses a concept of "session protection" which can be controlled via stateful and stateless...

It's a pretty straight forward concept: the backend of the system will keep the BSP application alive over several pages. Even when the whole browser is closed and reopened in the same page - the BSP session will simply contniue where it left off. Very handy when building multi-page (or even single page) applications. How can it be controlled ?

• Page properties: look for the properties that state "Statefull from here on", "Stateless from here on" and "Leave unchanged". The BSP application (as a whole) can also be started as statefull application from the BSP properties (rather than the page properties).
• In the event handlers (where the Runtime object is available) the state of the application can be changed (set or reset) as follows:

  * Set the BSP application to Statefull
  RUNTIME->KEEP_CONTEXT = 1. 

  and this would be a typical way to end the BSP application:

  * Set the BSP application to Stateless
  RUNTIME->KEEP_CONTEXT = 0. 
  NAVIGATION->EXIT( ).

This is a concept that you will need to try out to understand it.

Something to remember: when you are doing changes to a Layout of a BSP and you cannot make them visible from your browser, has the version you get in your browser been started in a Statefull mode ? The system will keep running with the same (old) version of your application... Just change the properties on the respective page to say "Stateless from here on" and the running application will pick it up. In general one of the first things you want to be available on your BSP application during development is the quit button...

• Prev
• Next