Design Pattern Observer (reverse)

Question

I have a set of objects that must perform a data acquisition and transmit to one class (many-to-one).

What is the best design pattern to achieve it? I thought about to use a "reverse" order of the Observer, but I am not sure if its a good idea.

Regards,

Your question is too vague to determine what pattern might be suitable. Please expand on the details of the scenario you are trying to solve. Pseudo-code for your data-source objects or destination object would be perfect. — Silas Reinagel
– Silas Reinagel, Commented Apr 6, 2015 at 20:04

Waog · Accepted Answer · 2015-04-07 14:12:07Z

2

No pattern required as far as your description goes.

Just hold a reference to the one class in every data acquisition class and call a method on the one class. Refactor it (e.g. with command or observer pattern) only when the need arises.

answered Apr 7, 2015 at 14:12

Waog

7,3155 gold badges28 silver badges39 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Erik Over a year ago

If the one class is a unique object, the singleton pattern could be used to ensure there is only one instance of that class. Furthermore, it can be used to decouple the singleton from the data acquisition classes: they do not need to keep a reference to the singleton object, but instead query the singleton class for the instance.

Collectives™ on Stack Overflow

Design Pattern Observer (reverse)

1 Answer 1

1 Comment

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Related