Restructure data flow on subscriber side

pgaudillere / ops

Automatically exported from code.google.com/p/ops

0 stars 0 forks source link

Restructure data flow on subscriber side #16

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago


1. TopicHandler should be created for each unique port/Receiver.

2. Subscribers adds them self as listeners for a certain topic from its 
TopicHandler.

This will be a more streamlined approach when extending to more transports 
and/or want to use one port for many topics.

Original issue reported on code.google.com by anton.gr...@gmail.com on 21 Sep 2009 at 5:00

GoogleCodeExporter commented 8 years ago

Original comment by anton.gr...@gmail.com on 21 Sep 2009 at 5:01

Added labels: Milestone-October_2009

GoogleCodeExporter commented 8 years ago

Original comment by anton.gr...@gmail.com on 22 Sep 2009 at 7:02

Changed state: Started

GoogleCodeExporter commented 8 years ago

Original comment by anton.gr...@gmail.com on 22 Sep 2009 at 5:53

Changed state: Fixed