Trace:
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
jvx:communication:async_callback [2018/01/31 21:38] admin |
jvx:communication:async_callback [2018/01/31 21:42] admin |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ~~Title: Asynchronous Communication using CallBac~~ | + | ~~Title: Asynchronous Communication using CallBack~~ |
Any function at the client´s business logic can be addressed using [[jvx:communication:calling_server_action|Server Actions]]. These are usually actions that do not take up a lot of time, such as, for example, input validation. | Any function at the client´s business logic can be addressed using [[jvx:communication:calling_server_action|Server Actions]]. These are usually actions that do not take up a lot of time, such as, for example, input validation. | ||
Line 15: | Line 15: | ||
Our application allows the creation of reports that are based on millions of datasets. However, the datasets have to be evaluated and compressed. Processing time for an individual report is approximately 3 minutes. | Our application allows the creation of reports that are based on millions of datasets. However, the datasets have to be evaluated and compressed. Processing time for an individual report is approximately 3 minutes. | ||
- | The user initiates the report by clicking a button (see Client Actions) and is notified when the report has been created. In the meantime, the user can continue to work as usual. | + | The user initiates the report by clicking a button (see [[jvx:client:gui:actions|Client Actions]]) and is notified when the report has been created. In the meantime, the user can continue to work as usual. |
As a first step, a server action is required: | As a first step, a server action is required: |