Multiple transport usage?

[cheme]

Difficult question. De facto peers must be the same (otherwhise simply use two dht instance)

• two dht sharing peermanagement : this could be done only by sharing peer type and having a special route implementation which runs a process for replying to both peermanagement process. Note that Peer type and KeyVal type must be shared!!! (or at least peer if we only shared the peer backend). Requires some evo to boot_server to use a closure for init : good evo.
• multiplex transport in a new transport with both, and add an index to interface (for choice), index value is calculated by rules over keyval and peers (to choose which transport to use). Receive of transport must run two synch thread cause two receive listen to, send is simplier. Here all is shared. Address type are multiplexed into transport.
  ??

second seems easiest to implement yet less generic