-snip- On 10/18/2017 10:50 AM, Ricardo Dias wrote:
Also, since we want to support multiple Ceph daemons (multiplexing) in the same process, what would be the preferable API (messenger <-> Ceph daemon) to be user: a) Instantiate a single Messenger object and share the instance between the multiple "sub-daemons" b) Each "sub-daemon" instantiates a Messenger object, and the internal Messenger code will take care of the magic of re-using/sharing the connections to the same peers.
I would recommend a) here. I was imagining each sub-daemon having its own Dispatcher, with a single Messenger instance for the process that fed its Messages into a MultiplexingDispatcher that knew how to steer them to the right sub-Dispatcher.
-- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
