Bug #52

State model/checking for modifications on InRouteConfigurators required

Added by J. Wienke almost 11 years ago. Updated almost 8 years ago.

Status:NewStart date:08/19/2010
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


Right now subscriptions on the router are passed to the port even if both are not activated. For the spread port this e.g. results on a call on the uninitialized connection right now and would need complex caching.


#1 Updated by S. Wrede almost 11 years ago

Could be fixed by State pattern implementation for active objects.

#2 Updated by J. Wienke over 10 years ago

  • Assignee changed from S. Wrede to J. Moringen

Jan, is this still a valid problem with the current implementation?

#3 Updated by J. Moringen over 10 years ago

Although we no longer have a Subscription class, the issue still persists for adding/removing Filters/Handlers to InRouteConfigurators. To resolve this, we probably need to do three things
  1. Specify acceptable method call sequences (or maybe use a state-centric terminology instead)
  2. Add test cases
  3. Enforce these constraints in the InRouteConfigurator implementation

#4 Updated by J. Wienke about 10 years ago

  • Subject changed from Router should only allow subscriptions after being activated to State model/checking for modifications on InRouteConfigurators required
  • Assignee deleted (J. Moringen)

#5 Updated by J. Wienke almost 8 years ago

From a user perspective this does not have any practical relevance anymore since all participants are now activated with their constructor. Should we drop this issue until someone stumbles across a real problem?

Also available in: Atom PDF