Hopefully, this effort will include thinking about how to factor that common part out into library form? Or perhaps a core event service and client bindings for interop? It would seem unfortunate if it was just internally shared code between two monolithic daemons.
I have never dug into the Android side of things, but wonder if there is a common ground that could serve the needs of server, desktop, laptop, mobile, router, and embedded environments. I realize that is asking a lot, particularly in terms of flexibility/performance/efficiency tradeoffs, but this feels like the kind of thing that could help keep Linux from branching off indefinitely into different niche platforms... I'm not even sure if it needs kernel side effort, given the latency and efficiency issues on mobile or embedded?