status-go/services
Andrea Maria Piana aa7f591587 Move networking code for waku under `v0` namespace
Why make the change?

As discussed previously, the way we will move across versions is to maintain completely separate
codebases and eventually remove those that are not supported anymore.

This has the drawback of some code duplication, but the advantage is that is more
explicit what each version requires, and changes in one version will not
impact the other, so we won't pile up backward compatible code.
This is the same strategy used by `whisper` in go ethereum and is influenced by
https://www.youtube.com/watch?v=oyLBGkS5ICk .

All the code that is used for the networking protocol is now under `v0/`.
Some of the common parts might still be refactored out.
The main namespace `waku` deals with `host`->`waku` interactions (through RPC),
while `v0` deals with `waku`->`remote-waku` interactions.

In order to support `v1`, the namespace `v0` will be copied over, and changed to
support `v1`. Once `v0` will be not used anymore, the whole namespace will be removed.

This PR does not actually implement `v1`, I'd rather get things looked over to
make sure the structure is what we would like before implementing the changes.

What has changed?

- Moved all code for the common parts under `waku/common/` namespace
- Moved code used for bloomfilters in `waku/common/bloomfilter.go`
- Removed all version specific code from `waku/common/const` (`ProtocolVersion`, status-codes etc)
- Added interfaces for `WakuHost` and `Peer` under `waku/common/protocol.go`

Things still to do

Some tests in `waku/` are still testing by stubbing components of a particular version (`v0`).
I started moving those tests to instead of stubbing using the actual component, which increases
the testing surface. Some other tests that can't be easily ported should be likely moved under
`v0` instead. Ideally no version specif code should be exported from a version namespace (for
example the various codes, as those might change across versions). But this will be a work-in-progress.

Some code that will be common in `v0`/`v1` could still be extract to avoid duplication, and duplicated only
when implementations diverge across versions.
2020-04-27 14:58:02 +02:00
..
accounts status-im/status-react#9203 Faster tx fetching with less request 2020-01-23 10:36:11 +02:00
browsers Use goimports instead of gofmt 2020-01-06 10:17:23 +01:00
ext Allow to leave chat without removing it 2020-04-14 14:08:54 +02:00
incentivisation Make shhext and protocol work with Waku (#1777) 2020-01-13 20:17:30 +01:00
mailservers remove eth.beta fleet as it has been decomissioned 2020-02-21 14:48:47 +01:00
nimbus Nimbus node support 2020-01-20 13:15:17 +01:00
nodebridge Initialize protocol when waku active (#1832) 2020-02-17 15:38:59 +01:00
peer Upgrade deps (#1892) 2020-03-09 08:55:58 +01:00
permissions Use goimports instead of gofmt 2020-01-06 10:17:23 +01:00
personal Use goimports instead of gofmt 2020-01-06 10:17:23 +01:00
rpcfilters Nimbus node support 2020-01-20 13:15:17 +01:00
shhext Ignore full node flag when in topic mode 2020-03-23 15:10:07 +01:00
status Upgrade deps (#1892) 2020-03-09 08:55:58 +01:00
subscriptions Avoid passing node to subscriptions service 2020-01-20 13:15:17 +01:00
typeddata Use goimports instead of gofmt 2020-01-06 10:17:23 +01:00
wakuext Move networking code for waku under `v0` namespace 2020-04-27 14:58:02 +02:00
wallet Stop fetching new blocks while app is not active 2020-03-11 08:39:41 +02:00
shhext_wakuext_test.go Split shhext into shhext and wakuext (#1803) 2020-01-20 21:56:06 +01:00
utils.go New debug_postSync endpoint (#1046) 2018-06-25 15:27:17 +02:00