Project

General

Profile

Task #3803

Avatar?id=6023&size=22x22

Task #3801: Improve EventBus implementation

Custom routings for events

Added by Andrzej Wójcik IoT 1 CloudTigaseTeam over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
2016-01-04
Due date:
% Done:

100%

Estimated time:
9.00 h
Database:
n/a

Description

In some cases as ie. for events sent between cluster nodes to pass informations from one user session to other user session of same user it is important to address this event to particular node in cluster as if we have user test@example.com connected to nodes node1 with resource res1 and to node2 with resource res2 in case of MessageCarbons we need to notify res2 that on res1 message carbons were enabled. In this case there is no need to forward this event to every cluster node as user session is only on nodes node1 and @node2@.

To do that it would be good to create RoutingEventHandler which could listen for particular event before event is sent and return list/set of nodes to which event should be forwarded.

Associated revisions

Revision b13e99a7 (diff)
Added by Andrzej Wójcik IoT 1 CloudTigaseTeam about 3 years ago

Issue #3803 - implementation of support for custom modifications for delivery of events to external systems (ie. to other cluster nodes)

Revision 1d80ff03 (diff)
Added by Andrzej Wójcik IoT 1 CloudTigaseTeam about 3 years ago

Issue #3803 - change in UserSessionEvent to allow to send it directly to single user session (session for particular resource)

Revision 64ec353c (diff)
Added by Andrzej Wójcik IoT 1 CloudTigaseTeam about 3 years ago

Issue #3803 and issue #3804 - fixed issues with EventRoutedTransientFillers and EventRouteSelectors, added possibility to stop event propagation on particular node if any EventRoutedTransientFiller for event returns false

History

#1 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam over 3 years ago

  • Assignee changed from Artur Hefczyc to Andrzej Wójcik
  • Estimated time set to 9.00 h

#2 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam about 3 years ago

  • Status changed from New to In QA
  • % Done changed from 0 to 80

I think that code is ready but will keep it in QA as I not tested this feature in runtime.

#3 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam about 3 years ago

  • Status changed from In QA to Closed

Tested in use during development and testing of #1601 - all works OK

#4 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam about 3 years ago

  • Assignee changed from Andrzej Wójcik to Artur Hefczyc

#5 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam about 3 years ago

  • % Done changed from 80 to 100

Also available in: Atom PDF