Return to Question

Also for the periodic timer the implementation is taken from this link of stackoverflow.

Also for the periodic timer the implementation is taken from this link of stackoverflow.

My Solution : This seems to me to be an observer pattern type problem, Hence I took the help and overview of observer pattern from stackexchange answer.

My Solution : This seems to me to be an observer pattern type problem, Hence I took the help and overview of observer pattern from stackexchange answer.

I have certain doubts like :

1. Is it too much overhead for publisher class. The timer management and to notify client at refresh_rate should be delegated too another class.

2. Should I use separate timer for every client or is there a better way to do it without timers at all.

3. Are the Event type and other enums for handling events and data used properly.

4. Is it better approach to have a function pointer from client for callback [as in the stackexchange link] rather than having client overload pure virtual function.

I have certain doubts like : [In bold are the suggestion as per @Edward]

1. Is it too much overhead for publisher class. The timer management and to notify client at refresh_rate should be delegated too another class. : Yes , may be use priority queue.

2. Should I use separate timer for every client or is there a better way to do it without timers at all. : The timer sleep and wake up time can managed using priority queue rather than every 1 sec.

3. Are the Event type and other enums for handling events and data used properly. : Use shared pointers and take care of typos

4. Is it better approach to have a function pointer from client for callback [as in the stackexchange link] rather than having client overload pure virtual function. : Yes, function pointers approach seems to be a better design