The PubSub implementation for go-libp2p https://github.com/libp2p/specs/tree/master/pubsub
Go to file
vyzo ef730627ad remove unnecessary and potentially harmful check from heartbeat
- the check is unnecessary because peers emit PRUNE on Leave
- the check is harmful, because the ANNOUNCE message might have
  benn lost (or reordered after the GRAFT depending on the retry
  strategy), which would leave the mesh in an inconsistent state.
2018-06-12 08:00:17 -07:00
.gx gx publish 0.9.17 2018-06-09 10:28:48 -07:00
ci Create Jenkinsfile 2017-11-27 13:15:23 +01:00
pb add gossipsub control messages 2018-06-12 08:00:17 -07:00
.gitignore gx publish v0.5.0 2016-09-14 15:27:34 -07:00
.travis.yml Disable sudo in Travis CI. 2017-11-17 23:04:19 -05:00
LICENSE use timecache 2016-09-10 20:47:12 -07:00
Makefile use timecache 2016-09-10 20:47:12 -07:00
README.md Updated README.md: Fixed 'go get' URL 2016-12-28 01:21:37 -08:00
codecov.yml Update Travis CI to use standard test script and go 1.9.x. 2017-11-17 22:36:56 -05:00
comm.go handle gossipsub control messages 2018-06-12 08:00:17 -07:00
floodsub.go add Join/Leave to PubSubRouter interface 2018-06-12 08:00:17 -07:00
floodsub_test.go basic gossipsub tests 2018-06-12 08:00:17 -07:00
gossipsub.go remove unnecessary and potentially harmful check from heartbeat 2018-06-12 08:00:17 -07:00
gossipsub_test.go test gossip propagation with IHAVE/IWANT cycle 2018-06-12 08:00:17 -07:00
mcache.go implement mcache 2018-06-12 08:00:17 -07:00
mcache_test.go fix go vet issues in mcache test 2018-06-12 08:00:17 -07:00
notify.go modularized pubsub; Flooding is just a routing method. 2018-01-27 09:54:57 +02:00
package.json gx publish 0.9.17 2018-06-09 10:28:48 -07:00
pubsub.go gossipsub: heartbeat timer 2018-06-12 08:00:17 -07:00
subscription.go add ctx to sub.Next for cancellation 2016-11-18 02:23:38 +01:00

README.md

go-floodsub

A flooding pubsub system.

Table of Contents

Install

go get github.com/libp2p/go-floodsub

Usage

TODO

Contribute

Contributions welcome. Please check out the issues.

Check out our contributing document for more information on how we work, and about contributing in general. Please be aware that all interactions related to multiformats are subject to the IPFS Code of Conduct.

Small note: If editing the README, please conform to the standard-readme specification.

License

MIT © Jeromy Johnson