Triggering an event on client-side while synchronizing state from the server is dangerous as the event might synchronizes inconsistent state back to the client.

Example:

1. Application listener is invoked as part of a round-trip
   1. Server removes column from ULCTable
   2. Server sets selection state in ULCComboBox
2. Server sends back responses to the client
3. Client handles responses from server
   1. Client handles remove column from server => table column state is marked as dirty
   2. Client handles set selection state from server
      1. Client sends current table column state back to server as table column state is marked dirty
      2. Client sends selection event back to server
4. Server handles requests from client
   1. Server handles remove column from client => this may lead to an error as this column is not part of the table anymore!