State model/checking for modifications on InRouteConfigurators required
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.
#3 Updated by J. Moringen over 9 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
- Specify acceptable method call sequences (or maybe use a state-centric terminology instead)
- Add test cases
- Enforce these constraints in the InRouteConfigurator implementation