close
This commit is contained in:
parent
6a41a615b9
commit
f324cfa9e7
2 changed files with 17 additions and 0 deletions
|
@ -37,3 +37,5 @@ I wondered if there is an easy way to restrict a single instance for some specia
|
||||||
[[!tag projects/datalad]]
|
[[!tag projects/datalad]]
|
||||||
|
|
||||||
[[!meta title="extend external special remote protocol so a process can refuse to PREPARE, making -J not use it concurrently"]]
|
[[!meta title="extend external special remote protocol so a process can refuse to PREPARE, making -J not use it concurrently"]]
|
||||||
|
|
||||||
|
> [[rejected|done]] --[[Joey]]
|
||||||
|
|
|
@ -0,0 +1,15 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 8"""
|
||||||
|
date="2020-09-28T14:00:00Z"
|
||||||
|
content="""
|
||||||
|
The async extension to the protocol guarantees only a single process will
|
||||||
|
be run. The remote might be asked to start several operations
|
||||||
|
concurrently, but if it wants to queue them sequentially, that should be
|
||||||
|
fine.
|
||||||
|
|
||||||
|
While it might be a bit of a round about way to get this functionality,
|
||||||
|
since the extension complicates the protocol a bit, I'm inclined to feel
|
||||||
|
it's enough, and not add this other extension,
|
||||||
|
at least without some more compelling use case.
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue