The Event Service is meant to be a central and uniform mechanism that allows event publishers/producers to talk to event subscribers/consumers. Its interface (IEventService) is a variation of the classic publish/subscribe pattern and the system implementation can be obtained by resolving the interface from the ObjectFactory.
Resolving the implementation this way allows its replacement with a custom one, in case this is needed. However, in most cases you can use the default implementation. To make the usage of the Event Service easier in the most common scenarios, the EventHub helper class is introduced, which always resolves the event service implementation and lets it do the real work.
NOTE: You should be careful with custom code when subscribing to events from EventHub. Once the SiteSync is completed, you should be careful not to trigger the events later, as this will cause problems. For example, if you subscribe to the IDynamicContentUpdatedEvent, you must not republish the dynamic content item on the production environment, because this will trigger the event and could cause unexpected behavior.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2019 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity