Comments

As noted in #706, we need a version of kvs_fence() that is non-blocking, and allows the response to be handled via an RPC continuation.

The KVS API is due for a rework anyway. I propose we go ahead and take a step in this direction by reworking kvs_fence(). Where I've been stuck before is in naming the two halves, especially when we'll have to split kvs_get(), since the second half might naturally have a _get suffix to match flux_rpc_get(). Her's a tentaive proposal: