Skip to content
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

Make transports a fixture of a router #16

Open
davidchappelle opened this issue Sep 10, 2015 · 0 comments
Open

Make transports a fixture of a router #16

davidchappelle opened this issue Sep 10, 2015 · 0 comments
Labels

Comments

@davidchappelle
Copy link
Collaborator

Since the original use cases for bonefish were very simple we made the specification of transports simple as well. As a result, transports are shared amongst routers. This needs to be inverted such that transports are configured on a router by router basis. As a result, transports can only be shared amongst the realms managed by a single router.

@davidchappelle davidchappelle changed the title [feature] Make transports a fixture of a router Make transports a fixture of a router Nov 5, 2015
nlyan pushed a commit to symless/bonefish that referenced this issue Jul 13, 2017
Add base32_hex codec variant, a.k.a. base32hex from RFC 4648.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant