Life cycle of page, execution, desktop, session, application"

From Documentation
m
m (correct highlight (via JWB))
 
Line 4: Line 4:
 
*page
 
*page
 
: A single page.
 
: A single page.
*execution<ref><tt>execution</tt> in ZK is a wrapper of <tt>request</tt> in JSP </ref>
+
*execution<ref><code>execution</code> in ZK is a wrapper of <code>request</code> in JSP </ref>
 
: Processing a request from client side. It can cross pages.
 
: Processing a request from client side. It can cross pages.
 
*desktop
 
*desktop

Latest revision as of 10:36, 19 January 2022

Life cycle of page, execution, desktop, session, application


Stop.png This documentation is for an older version of ZK. For the latest one, please click here.


From small scope to big:

  • page
A single page.
Processing a request from client side. It can cross pages.
  • desktop
All pages serving the same URL, for one browser tab.
  • session
From user visit the web to user leave or timeout. All following pages are related to same session.
  • application
From the application service start to stop. It is cross session, cross users.

Note that, if you press "F5" to refresh the web page, it's a different desktop, but the same session.

Note

  1. execution in ZK is a wrapper of request in JSP



Last Update : 2022/01/19

Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License.