Event Firing"
m (→Echo an Event) |
|||
| Line 41: | Line 41: | ||
= Echo an Event = | = Echo an Event = | ||
| − | Echoing | + | Echoing is a way to delay the event processing until the next AU request (aka., Ajax) is received. |
| − | More precisely, the event being echoed won't be queued into the event queue. Rather, it | + | More precisely, the event being echoed won't be queued into the system event queue. Rather, it asks the client to send back an AU request immediately. Furthermore, after the server receives the AU request, the event is then posted to the system event queue for processing. |
In other words, the event won't be processed in the current execution. Rather, it is processed in the following request when the event is <i>echoed</i> back from the client. | In other words, the event won't be processed in the current execution. Rather, it is processed in the following request when the event is <i>echoed</i> back from the client. | ||
| Line 51: | Line 51: | ||
</source> | </source> | ||
| − | Event echoing is useful for implementing a long operation. HTTP is a request-and-response protocol, so the user won't see any feedback until the request has been served and responsed. Thus, | + | Event echoing is useful for implementing a long operation. HTTP is a request-and-response protocol, so the user won't see any feedback until the request has been served and responsed. Thus, we could send back some busy message to let the user know what happens, and echo back an event to do the long operation. For more information, please refer to the [[ZK Developer's Reference/UI Patterns/Long Operations/Use Echo Events|Long Operations: Use Echo Events]] section. |
=Version History= | =Version History= | ||
Revision as of 10:33, 2 December 2010
Events are usually fired (aka., triggered) by a component (when serving the user at the client). However, applications are allowed to fire events too.
There are three ways to trigger an event: post, send and echo.
Post an Event
Posting is the most common way to trigger an event. By posting, the event is placed at the end of the system event queue[1]. Events stored in the system event queue are processed one-by-one in first-in-first-out order. Each desktop has one system event queue and all events are handled sequentially.
To trigger an event, you could invoke Events.postEvent(String, Component, Object). For example,
Events.postEvent("onClick", button, null); //simulate a click
In additions to post an event to the end of the system event queue, you could specify a priority with Events.postEvent(int, String, Component, Object). By default, the priority is 0. The higher the priority the earlier an event is processed.
Notice that the invocation returns after placing the event to the system event queue. In other words, the event won't be processed unless all other events posted earlier or with higher priority are processed.
- ↑ Please don't confuse it with the event queues discussed in the event queues section, which are application-specific, while the system event queue is invisible to application developers.
Send an Event
If you prefer to trigger an event to a component directly and process it immediately, rather than placing in the system event queue and waiting for execution, you could use Events.sendEvent(String, Component, Object) to trigger the event.
Events.sendEvent("onMyEvent", component, mydata);
Events.sendEvent(String, Component, Object) won't return until all handlers and listeners registered for this event has been processed. You could image it as a method invocation. Also notice that the event handlers and listeners are invoked directly without starting any event thread (no matter the event thread is enabled or not[1]).
Echo an Event
Echoing is a way to delay the event processing until the next AU request (aka., Ajax) is received.
More precisely, the event being echoed won't be queued into the system event queue. Rather, it asks the client to send back an AU request immediately. Furthermore, after the server receives the AU request, the event is then posted to the system event queue for processing.
In other words, the event won't be processed in the current execution. Rather, it is processed in the following request when the event is echoed back from the client.
Events.echoEvent("onMyEvent", component, mydata);
Event echoing is useful for implementing a long operation. HTTP is a request-and-response protocol, so the user won't see any feedback until the request has been served and responsed. Thus, we could send back some busy message to let the user know what happens, and echo back an event to do the long operation. For more information, please refer to the Long Operations: Use Echo Events section.
Version History
| Version | Date | Content |
|---|---|---|