-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implement async kvs_fence()
call
#707
Comments
garlick
added a commit
to garlick/flux-core
that referenced
this issue
Jun 24, 2016
Split kvs_fence() into kvs_fence_begin() and kvs_fence_finish(). Fixes flux-framework#707.
garlick
added a commit
to garlick/flux-core
that referenced
this issue
Jun 28, 2016
Split kvs_fence() into kvs_fence_begin() and kvs_fence_finish(). Fixes flux-framework#707.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 splitkvs_get()
, since the second half might naturally have a_get
suffix to matchflux_rpc_get()
. Her's a tentaive proposal:Current blocking prototype:
Proposed new prototypes:
The text was updated successfully, but these errors were encountered: