Hx uses
Events to provide background interaction between the server
and the browser. Events always originate from the client browser, and must
return executable javascript as the response (you are not required to return
content). The html form is encoded and sent for every event fire, so
op.getFormValue() can be used to query the browser page state.
Events are implemented on top of the HxView.process
method, and therefore use the XmlHttp support implemented in the
major browsers.
Command extends
Event to add some convenience methods and a display name property.
By convention Commands are triggered by the user (maybe by
clicking on a button), while Events are triggered
programmatically. Though in reality they are interchangeable.
Note: javax.baja.hx.Command is not the same class as the
javax.baja.ui.Command.