Echo Event Handling"
From Documentation
(Created page with "{{ZATSEssentialsPageHeader}} Since 1.1.0 {{ZATSEssentialsPageHeader}} {{ZATSEssentialsPageFooter}}") |
|||
| Line 2: | Line 2: | ||
Since 1.1.0 | Since 1.1.0 | ||
| + | [[ZK%20Developer's%20Reference/UI%20Patterns/Long%20Operations/Use%20Echo%20Events| Echo event]] is used to implement long operations. When you send an echo event, the event won't be processed in the current execution. Rather, it is processed in the next AU request sent (echoed back) from the client. In this new release, Mimic <tt>Client</tt> are now capable of simulating an echo event. By default, Mimic <tt>Client</tt> sends the echoed AU request immediately after receiving an echo event. However, you can change it by the method below: | ||
| + | <source lang='java'> | ||
| + | Client.setEchoEventMode(EchoEventMode.PIGGYBACK); | ||
| + | </source>. | ||
| + | |||
| + | Mimic <tt>Client</tt> will then send custom events back to server together with the next AU request instead of sending it back immediately. | ||
Revision as of 05:55, 26 April 2013
Since 1.1.0
Echo event is used to implement long operations. When you send an echo event, the event won't be processed in the current execution. Rather, it is processed in the next AU request sent (echoed back) from the client. In this new release, Mimic Client are now capable of simulating an echo event. By default, Mimic Client sends the echoed AU request immediately after receiving an echo event. However, you can change it by the method below:
Client.setEchoEventMode(EchoEventMode.PIGGYBACK);
.
Mimic Client will then send custom events back to server together with the next AU request instead of sending it back immediately.