Skip to content
This repository has been archived by the owner on Apr 24, 2023. It is now read-only.

Create an illustration of how WebRTC Star network is set up (Rendezvous point at the middle) #117

Open
daviddias opened this issue Aug 31, 2017 · 3 comments
Labels
exp/expert Having worked on the specific codebase is important help wanted Seeking public contribution on this issue status/ready Ready to be worked

Comments

@daviddias
Copy link
Member

No description provided.

@daviddias daviddias added status/ready Ready to be worked help wanted Seeking public contribution on this issue exp/expert Having worked on the specific codebase is important labels Feb 5, 2018
@Ivshti
Copy link

Ivshti commented Mar 25, 2018

@diasdavid can we have a bit more clarification on this?

  1. As far as I can see, the signalling server is only used to exchange mutladdr's, rather than a full ICE connectivity description - am I understand this right?
  2. This would mean there is no TURN fallback, is that correct?

@daviddias
Copy link
Member Author

As far as I can see, the signalling server is only used to exchange mutladdr's, rather than a full ICE connectivity description - am I understand this right?

No. The SS is really exchanging the SDP offers and uses multiaddrs to route them properly

This would mean there is no TURN fallback, is that correct?

This is correct.

@harrshasri
Copy link

harrshasri commented Apr 17, 2018

@diasdavid @lidel
Hi, I David I was able to integrate ipfs in my Github for Shopping Extension using PubSub Mechanism. But with websocket-star config. I wonder how the pubsub works in websocket-star layer.

  1. Is it a Flooding Technique among the publishers and subscribers of a Topic via the signalling server?
  2. I hope there is no content routing within the pubsub

Because I want to scale this App with less data transfer among the peers. Do you suggest doing PubSub on top of DHT. When it is done.

I was confused because there is no proper documentation for websocket-star transport mechanism

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
exp/expert Having worked on the specific codebase is important help wanted Seeking public contribution on this issue status/ready Ready to be worked
Projects
None yet
Development

No branches or pull requests

3 participants