|
| 1 | +# [Transports](http://libp2p.io/implementations/#transports) |
| 2 | + |
| 3 | +libp2p doesn't make assumptions for you, instead, it enables you as the developer of the application to pick the modules you need to run your application, which can vary depending on the runtime you are executing. A libp2p node can use one or more Transports to dial and listen for Connections. These transports are modules that offer a clean interface for dialing and listening, defined by the [interface-transport](https://github.com/libp2p/interface-transport) specification. Some examples of possible transports are: TCP, UTP, WebRTC, QUIC, HTTP, Pigeon and so on. |
| 4 | + |
| 5 | +A more complete definition of what is a transport can be found on the [interface-transport](https://github.com/libp2p/interface-transport) specification. A way to recognize a candidate transport is through the badge: |
| 6 | + |
| 7 | +[](https://raw.githubusercontent.com/diasdavid/interface-transport/master/img/badge.png) |
| 8 | + |
| 9 | +## 1. Creating a libp2p Bundle with TCP |
| 10 | + |
| 11 | +When using libp2p, you always want to create your own libp2p Bundle, that is, pick your set of modules and create your network stack with the properties you need. In this example, we will create a bundle with TCP. You can find the complete solution on the file [1.js](/1.js). |
| 12 | + |
| 13 | +You will need 4 deps total, so go ahead and install all of them with: |
| 14 | + |
| 15 | +``` |
| 16 | +> npm install libp2p libp2p-tcp peer-info async |
| 17 | +``` |
| 18 | + |
| 19 | +Then, on your favorite text editor create a file with the `.js` extension. I've called mine `1.js`. |
| 20 | + |
| 21 | +First thing is to create our own bundle! Insert: |
| 22 | + |
| 23 | +```JavaScript |
| 24 | +'use strict' |
| 25 | + |
| 26 | +const libp2p = require('libp2p') |
| 27 | +const TCP = require('libp2p-tcp') |
| 28 | +const PeerInfo = require('peer-info') |
| 29 | +const waterfall = require('async/waterfall') |
| 30 | + |
| 31 | +// This MyBundle class is your libp2p bundle packed with TCP |
| 32 | +class MyBundle extends libp2p { |
| 33 | + constructor (peerInfo) { |
| 34 | + // modules is a JS object that will describe the components |
| 35 | + // we want for our libp2p bundle |
| 36 | + const modules = { |
| 37 | + transport: [new TCP()] |
| 38 | + } |
| 39 | + super(modules, peerInfo) |
| 40 | + } |
| 41 | +} |
| 42 | +``` |
| 43 | + |
| 44 | +Now that we have our own MyBundle class that extends libp2p, let's create a node with it. We will use `async/waterfall` just for code structure, but you don't need to. Append to the same file: |
| 45 | + |
| 46 | +```JavaScript |
| 47 | +let node |
| 48 | + |
| 49 | +waterfall([ |
| 50 | + // First we create a PeerInfo object, which will pack the |
| 51 | + // info about our peer. Creating a PeerInfo is an async |
| 52 | + // operation because we use the WebCrypto API |
| 53 | + // (yeei Universal JS) |
| 54 | + (cb) => PeerInfo.create(cb), |
| 55 | + (peerInfo, cb) => { |
| 56 | + // To signall the addresses we want to be available, we use |
| 57 | + // the multiaddr format, a self describable address |
| 58 | + peerInfo.multiaddrs.add('/ip4/0.0.0.0/tcp/0') |
| 59 | + // Now we can create a node with that PeerInfo object |
| 60 | + node = new MyBundle(peerInfo) |
| 61 | + // Last, we start the node! |
| 62 | + node.start(cb) |
| 63 | + } |
| 64 | +], (err) => { |
| 65 | + if (err) { throw err } |
| 66 | + |
| 67 | + // At this point the node has started |
| 68 | + console.log('node has started (true/false):', node.isOn()) |
| 69 | + // And we can print the now listening addresses. |
| 70 | + // If you are familiar with TCP, you might have noticed |
| 71 | + // that we specified the node to listen in 0.0.0.0 and port |
| 72 | + // 0, which means "listen in any network interface and pick |
| 73 | + // a port for me |
| 74 | + console.log('listening on:') |
| 75 | + node.peerInfo.multiaddrs.forEach((ma) => console.log(ma.toString())) |
| 76 | +}) |
| 77 | +``` |
| 78 | + |
| 79 | +Running this should result in somehting like: |
| 80 | + |
| 81 | +```bash |
| 82 | +> node 1.js |
| 83 | +node has started (true/false): true |
| 84 | +listening on: |
| 85 | +/ip4/127.0.0.1/tcp/61329/ipfs/QmW2cKTakTYqbQkUzBTEGXgWYFj1YEPeUndE1YWs6CBzDQ |
| 86 | +/ip4/192.168.2.156/tcp/61329/ipfs/QmW2cKTakTYqbQkUzBTEGXgWYFj1YEPeUndE1YWs6CBzDQ |
| 87 | +``` |
| 88 | + |
| 89 | +That `QmW2cKTakTYqbQkUzBTEGXgWYFj1YEPeUndE1YWs6CBzDQ` is the PeerId that was created during the PeerInfo generation. |
| 90 | + |
| 91 | +## 2. Dialing from one node to another node |
| 92 | + |
| 93 | +Now that we have our bundle, let's create two nodes and make them dial to each other! You can find the complete solution at [2.js](/2.js). |
| 94 | + |
| 95 | + |
| 96 | + |
| 97 | +## 3. Using multiple transports |
| 98 | + |
| 99 | +- show TCP + websockets |
| 100 | + |
| 101 | +## 4. How to create a new libp2p transport |
| 102 | + |
| 103 | +- interface-transport |
| 104 | +- follow the interface |
| 105 | +- show other examples (webrtc, utp, udt (wip), etc) |
| 106 | +- |
0 commit comments