The readData() operation should be pretty straightforward, but we have kinks in place.

First of all, there is the magic 'create YANG notification streams' bit, which is synchronous and should not even be present.

Second of all, there is the whole 'withFields' and 'withDefaults' processing, which requires synchronous reads in RestconfStrategy. These need some figuring out, but not much:

1. current implementation should be in MdsalRestconfStrategy, really
2. NETCONF should do its own thing for withFields based on NetconfDataTreeService
3. NETCONF's stance to withDefaults needs to be fixed. Essentially if the device supports it, great, we will pass it down. If not ... that's tricky, as we can just reject the invocation, or do some fudging based on RFC6243 spec.

As part of this issue we want to specialize the 'read whole datastore' and 'read a particular resource', e.g. the difference in identifier being null.

When the dust around all of this settles, RestconfStrategy.readData() should return a RestconfFuture and just perform result mapping based on that – completing an AsyncResponse.