Group connection state management: is this really necessary?
Group internal repository implementation: somehow find out if we can get rid of all the void pointer handling. right now I am missing a replacement of reinterpret_cast for shared_ptrs. The underlying problem is that Converter uses references and hence no Repository<void> can be declared as a polymorphic base type for the generic handling by name
Group internal repository implementation: somehow find out if we can get rid of all the void pointer handling. right now I am missing a replacement of reinterpret_cast for shared_ptrs. The underlying problem is that Converter uses references and hence no Repository<void> can be declared as a polymorphic base type for the generic handling by name
Group internal repository implementation: somehow find out if we can get rid of all the void pointer handling. right now I am missing a replacement of reinterpret_cast for shared_ptrs. The underlying problem is that Converter uses references and hence no Repository<void> can be declared as a polymorphic base type for the generic handling by name
Class rsb::eventprocessing::OutRouteConfigurator: add configuration, provide preliminary set up interface
Class rsb::filter::FilterObserver: Check if Double Dispatch pattern is best suited here
Class rsb::Listener: use templates in subscriptions only? (however, they need the event info)
Class rsb::spread::MembershipManager: think about adding SpreadConnectionPtr as a member, offering methods that operate on this connection only
Member rsb::spread::SpreadConnection::getMailbox (): why pointer? mailbox is a typedef to int? If pointer is required use a shared ptr