On 15/04/2016, Milosz Tanski wrote:
[snip]
> As librados is today, it encapsulates it's own networking and event
> code. This is pretty frustrating to apps that already have their own
> eventloop that want to integrate it.
When you say integrating with an event loop, would being able to hand off a
function or object to asynchronous calls that would then use whatever mechanism
your event loop had for submitting events be sufficient?
I'm not sure what you mean by networking in this case. Some means for the
library to ask your client to set up or terminate a connection when it needs to
talk to an OSD or monitor?
--
Senior Software Engineer Red Hat Storage, Ann Arbor, MI, US
IRC: Aemerson@{RedHat, OFTC, Freenode}
0x80F7544B90EDBFB9 E707 86BA 0C1B 62CC 152C 7C12 80F7 544B 90ED BFB9
--
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
