Designing the communication API with the drivers is actually the easy part.

The hard part is:

• actual implementation (resumable push is a challenge)
• find the proper abstraction in go world

Here are some things that we want to take into account:

• the possibility to have language-agnostic drivers might be a plus - that would obviously mean we need an agnostic transport (http, spdy, ...)
• we want to have a communication channel that is extremely robust and reasonably "simple" to debug in order not to add too much complexity on top of the driver itself
• ability to NOT having to recompile the registry itself to enjoy using new drivers is definitely something to consider

@noxiouz @bacongobbler