Skip to content
This repository has been archived by the owner on Dec 20, 2023. It is now read-only.

Better support for multiple Weave client processes on single host #367

Open
jaylogue opened this issue Sep 13, 2019 · 1 comment
Open

Better support for multiple Weave client processes on single host #367

jaylogue opened this issue Sep 13, 2019 · 1 comment
Assignees
@jaylogue

Comments

@jaylogue
Copy link
Contributor

Modify the Weave Message Layer and associated code to better support multiple Weave-enabled processes operating as independent clients on a single host. This should include:

  • The ability to initiate outbound TCP and UDP communications from an ephemeral port.

  • The ability to disable TCP/UDP listening on the standard Weave port.

  • Automatic assignment of unique device ids to client instances.
@jaylogue jaylogue self-assigned this Sep 13, 2019
@gerickson
Copy link
Contributor

+1

@jaylogue jaylogue mentioned this issue Oct 23, 2019
Merged
@gerickson gerickson mentioned this issue Jun 9, 2020
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jaylogue jaylogue

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gerickson @jaylogue