You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, names of dnpipes can conflict across different participants because unlike their local cousins a dnpipe doesn't live in a hierarchical filesystem but in a flat namespace. There are two options one can imagine: allow conflicts and let participants resolve it themselves or suggest a namespace scheme, for example, based on (distributed) process ID (as the case with Marathon) or even a DNS-based solution.
The text was updated successfully, but these errors were encountered:
Currently, names of dnpipes can conflict across different participants because unlike their local cousins a dnpipe doesn't live in a hierarchical filesystem but in a flat namespace. There are two options one can imagine: allow conflicts and let participants resolve it themselves or suggest a namespace scheme, for example, based on (distributed) process ID (as the case with Marathon) or even a DNS-based solution.
The text was updated successfully, but these errors were encountered: