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
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
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
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.
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.
mainnet-milestone1
.TCPTransport
stuff topkg/network
module.network.Config
.tcpC
member tonetwork.Network
.Network.Init()
(if needed).Network.Close()
.Network.TCP() *TCPFactory
field.Network.Dial()
andNetwork.Listen()
to be able to dial/listen with"tcp"
."tcp"
options to:public-key:ip-address
table tovisor.Config
which in turn gets copied tonetwork.Config
and then used bynetwork.TCPFactory
.TCPFactory
.The text was updated successfully, but these errors were encountered: