eEngineEvents Fields

Engine received a Blob Object

RETIRED IN V4: No more channels

RETIRED IN V4: No more channels

RETIRED IN V4: No more channels

Fires when the ContentService receives a CDE_CHECK4UPDATES request from another node.

Fires when a new chunk of a larger telegram was received

A plugin-service can subscribe to this event in order to update the costing for the telegram. The Event is called synchronously and should be used ONLY to update the costing of the Telegram

Any Message sent to the Content-Relay Service that was not handled by the Content Service will be forwarded to this event

Register a callback that will be called when the engine was started (via Start Engine)

Register a callback to handle the event that is fired when the engine was stopped. For LiveEngine/Service data provider this only happens during shutdown of the hosting application For Not LiveEngines/Data Consumer this happens when the last communication channel was lost and no more channels are active

This event is called when a plugin-service has "ProcessInitialized()" SetEngineReadiness() method

This event is called when a plugin-service was set to Ready using the SetEngineReadiness() method

Fired when a file is received by the C-DEngine. a plugin can register for this event and gets notified if the file was meant for the it

This event behaves similarly to eEngineEvents.IncomingMessage, but is also fired subsequently to eThingEvents.IncomingMessage. Any time either eThingEvents.IncomingMessage or eEngineEvents.IncomingMessage is fired, this event will also be fired. Be aware that subscribing to this event along with one (or more) of the other IncomingMessage events on the same Thing/engine may cause you to receive duplicate messages.

This is the main event handler for all incoming telegrams. It will be called if all underlying security and scoping conditions are met.

Register a callback that will be called when a TSM was processed This allows for communication between plugin-services

RETIRED IN V4: No more channels

Can be fired on the ContentService to announce a new Event Log Events

A new Subscription was received for the Engine

C-DEngine is about to shutdown. The MyServiceHostInfo.PreShutDownDelay sets the delay time for the shutdown. By default this is zero and the event is not fired

Fires when the Engine received a Shut Down request "StopEngine()"

Fired when a Thing of an engine was Deleted from the Registry

NEWV4: Fired when RegisterThing has called the Init() function

Fired when a new Thing of an engine was registereed

Fired when a Thing of an Engine was updated