You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by da...@apache.org on 2014/03/20 23:09:46 UTC
svn commit: r1579793 -
/isis/site/trunk/content/reference/services/publishing-service.md
Author: danhaywood
Date: Thu Mar 20 22:09:46 2014
New Revision: 1579793
URL: http://svn.apache.org/r1579793
Log:
event bus service
Modified:
isis/site/trunk/content/reference/services/publishing-service.md
Modified: isis/site/trunk/content/reference/services/publishing-service.md
URL: http://svn.apache.org/viewvc/isis/site/trunk/content/reference/services/publishing-service.md?rev=1579793&r1=1579792&r2=1579793&view=diff
==============================================================================
--- isis/site/trunk/content/reference/services/publishing-service.md (original)
+++ isis/site/trunk/content/reference/services/publishing-service.md Thu Mar 20 22:09:46 2014
@@ -184,7 +184,7 @@ An alternative implementation of the `Ev
## Related Services
-The `PublishingService` is intended for coarse-grained publish/subscribe for system-to-system interactions, from Isis to some other system. Here the only events published are those that action invocations (for actions annotated with [`@PublishedAction`](../recognized-annotations/PublishedAction.html)) and of changed objects (for objects annotated with [`@PublishedObject`](../recognized-annotations/PublishedObject.html).
+The `PublishingService` is intended for coarse-grained publish/subscribe for system-to-system interactions, from Isis to some other system. Here the only events published are those that action invocations (for actions annotated with [`@PublishedAction`](../recognized-annotations/PublishedAction.html)) and of changed objects (for objects annotated with [@PublishedObject](../recognized-annotations/PublishedObject.html).
The [EventBusService](./event-bus-service.html) meanwhile is intended for fine-grained publish/subscribe for object-to-object interactions within an Isis domain object model. The event propogation is strictly in-memory, and there are no restrictions on the object acting as the event (it need not be serializable, for example).