4 ms·
web2: client <-> server web3: client <-> client <-> client
by agustif 5y ago
web2: client <-> server
web3: client <-> client <-> client
- semicolon_storm 5y agoWhen's a client become a server? If you need to connect to a fullnode which is running in a datacenter somewhere whose sole purpose is to service these kinds of requests, surely it's just a server.
- pphysch 5y agoweb1: client <-> client Web2 happened for a lot of very good reasons.
- Matthias247 5y agoFrom the blog post I understood this still talks from the browser client to some gateway server, which might then be part of a p2p network. Which would certainly be required if the library uses http for communication. Or did I got it wrong and a native browser plugin enables other means of communication?