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

Implement ability to switch between transport types (dmsg and tcp transport). #501

Open
10 tasks
ayuryshev opened this issue Jul 25, 2019 · 0 comments
Open
10 tasks
Assignees
Labels
Milestone

Comments

@ayuryshev
Copy link
Collaborator

ayuryshev commented Jul 25, 2019

Feature description

Implement ability to specify between different underlying network connection types when saving transports.

Important notes

Communication between setup nodes and visor nodes SHOULD ALWAYS be via dmsg.
Electable network types should only be done for transports.

Tasks

These tasks should be done in the given order.

@ayuryshev ayuryshev changed the title Feature: Use transport.TCPFactory/transport.TCPTransport alongside dmsg.Client/dmsg.Transport Feature: Use transport.TCPFactory/transport.TCPTransport instead/alongside dmsg.Client/dmsg.Transport Jul 25, 2019
@ayuryshev ayuryshev self-assigned this Jul 25, 2019
@evanlinjin evanlinjin changed the title Feature: Use transport.TCPFactory/transport.TCPTransport instead/alongside dmsg.Client/dmsg.Transport Implement ability to switch between transport types (dmsg and tcp transport). Aug 16, 2019
@evanlinjin evanlinjin added this to the Milestone 1 milestone Aug 16, 2019
ayuryshev referenced this issue in ayuryshev/skywire Aug 27, 2019
Excluding the last task defined  in skycoin/skywire#501 - everything is completed.

It was already done by most part a long time before.

The most hard part is in the last task.
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

2 participants