CSA_Events - Client/server events
Client/server events are events, which are sent from an ODABA server to its clients. When data on server changes, the server will notify all clients, which are registered for the updated database entry. In order to register database resources on the server, Property::register() has to be called after opening the property.
Client/server events are passed asynchronously to the client, which receives a notify message. In order to handle server events, the client has to implement Notify...() handlers in appropriate context classes or event handlers assigned to the property.
Enumarators overview
- SE_Close
(19) - Closing server access handle
- SE_Command
(13) - Server to Client command
- SE_Create
(14) - Creating instance on server side
- SE_Delete
(18) - Deleting instance on server side
- SE_Dirty
(21) - Indicates inconsistency between client and server
- SE_Insert
(16) - Inserting instance on server side
- SE_Open
(11) - Server object has been opened
- SE_Remove
(17) - Removing instance on server side
- SE_Update
(15) - Updating instance on server side
Enumerator details
-
CE_Open - Server object has been opened
The event is a access handle event that is sent when an registered access handle has been opened on the server.
When the event is generated, the access handle is not yet accessible.
The event can be handled in property context by overloading the PropertyContext::notifyOpen() handler.
Code: 1
to list -
CE_Opened - Server object has been opened
The event is a access handle event that is sent when an registered access handle has been opened on the server.
When the event is generated, the access handle is not yet accessible.
The event can be handled in property context by overloading the PropertyContext::notifyOpened() handler.
Code: 2
to list -
CE_Command - Server to Client command
The event is a property event that is sent from business rules running on server in order to submit requests to the client. The command is passed as a string containing the command name and a parameter string separated by a blank.
When the event is generated, the property is accessible.
The event can be handled in property context by overloading the PropertyContext::executeCommand() handler.
Code: 3
to list -
CE_Create - Creating instance on server side
The event is a type event that is sent when an instance has been created on the server.
When the event is generated, the property is accessible.
The event can be handled in property context by overloading the PropertyContext::notifyCreate() handler.
Code: 4
to list -
CE_Update - Updating instance on server side
The event is a type event that is sent when an instance has been updated.
When the event is generated, the property is accessible.
The event can be handled in property context by overloading the PropertyContext::notifyUpdate() handler.
Code: 5
to list -
CE_Insert - Inserting instance on server side
The event is a property event that is sent when an instance has been inserted to a collection.
When the event is generated, the property is accessible.
The event can be handled in property context by overloading the PropertyContext::notifyInsert() handler.
Code: 6
to list -
CE_Remove - Removing instance on server side
The event is a property event that is sent when an instance has been removed from a collection.
When the event is generated, the property is accessible.
The event can be handled in property context by overloading the PropertyContext::notifyRemove() handler.
Code: 7
to list -
CE_Delete - Deleting instance on server side
The event is a type event that is sent when an instance has been deleted on the server.
When the event is generated, the property is accessible.
The event can be handled in property context by overloading the PropertyContext::notifyDelete() handler.
Code: 8
to list -
CE_Close - Closing server access handle
The event is a property event that is sent when a property handle on server has been closed.
When the event is generated, the property is not accessible anymore.
The event can be handled in property context by overloading the PropertyContext::notifyClose() handler.
Code: 9
to list -
CE_Closed - Server access handle has been closed
The event is a property event that is sent when a property handle on server has been closed.
When the event is generated, the property is not accessible anymore.
The event can be handled in property context by overloading the PropertyContext::notifyClosed() handler.
Code: 10
to list -
SE_Open - Server object has been opened
The event is a access handle event that is sent when an registered access handle has been opened on the server.
When the event is generated, the access handle is not yet accessible.
The event can be handled in property context by overloading the PropertyContext::notifyOpen() handler.
Code: 11
to list -
SE_Opened - Server object has been opened
The event is a access handle event that is sent when an registered access handle has been opened on the server.
When the event is generated, the access handle is not yet accessible.
The event can be handled in property context by overloading the PropertyContext::notifyOpened() handler.
Code: 12
to list -
SE_Command - Server to Client command
The event is a property event that is sent from business rules running on server in order to submit requests to the client. The command is passed as a string containing the command name and a parameter string separated by a blank.
When the event is generated, the property is accessible.
The event can be handled in property context by overloading the PropertyContext::executeCommand() handler.
Code: 13
to list -
SE_Create - Creating instance on server side
The event is a type event that is sent when an instance has been created on the server.
When the event is generated, the property is accessible.
The event can be handled in property context by overloading the PropertyContext::notifyCreate() handler.
Code: 14
to list -
SE_Update - Updating instance on server side
The event is a type event that is sent when an instance has been updated.
When the event is generated, the property is accessible.
The event can be handled in property context by overloading the PropertyContext::notifyUpdate() handler.
Code: 15
to list -
SE_Insert - Inserting instance on server side
The event is a property event that is sent when an instance has been inserted to a collection.
When the event is generated, the property is accessible.
The event can be handled in property context by overloading the PropertyContext::notifyInsert() handler.
Code: 16
to list -
SE_Remove - Removing instance on server side
The event is a property event that is sent when an instance has been removed from a collection.
When the event is generated, the property is accessible.
The event can be handled in property context by overloading the PropertyContext::notifyRemove() handler.
Code: 17
to list -
SE_Delete - Deleting instance on server side
The event is a type event that is sent when an instance has been deleted on the server.
When the event is generated, the property is accessible.
The event can be handled in property context by overloading the PropertyContext::notifyDelete() handler.
Code: 18
to list -
SE_Close - Closing server access handle
The event is a property event that is sent when a property handle on server has been closed.
When the event is generated, the property is not accessible anymore.
The event can be handled in property context by overloading the PropertyContext::notifyClose() handler.
Code: 19
to list -
SE_Closed - Server access handle has been closed
The event is a property event that is sent when a property handle on server has been closed.
When the event is generated, the property is not accessible anymore.
The event can be handled in property context by overloading the PropertyContext::notifyClosed() handler.
Code: 20
to list -
SE_Dirty - Indicates inconsistency between client and server
The event is an object space event that is sent from a replication server, when data on the server has been changed by another client.
The event is handled by the system.
Code: 21
to list