search

boplish / core

Browser-based Open Publishing core libraries
Other
24 stars 1 forks source link

Not working when using Firefox and Chrome concurrently #8

Closed RoundSparrow closed 10 years ago

RoundSparrow commented 10 years ago

Now shows the activity and serves up the demo page... but two instances of browser on the same node server (Localhost 5000) are not showing up in the peer list.

Can I turn on some kind of debugging output to the javascript console (or better yet, some on-html debug output?)

UPDATE: So it seems that there is an issue with having a Chrome client alive ont he same Node server. I had started out with two Chrome 31 clients and found that it wasn't working... I never closed them when I opened up Firefox 25... and once I closed the Chrome clients the two Firefox 25 clients start working.

Can you confirm that problem?

chris-- commented 10 years ago

Does the Message Inspector show any messages (IN/OUT) at all? There is a running implementation here that is using the node.js bootstrap server.

RoundSparrow commented 10 years ago

Please see the update in my first post. It seems that putting a Chrome client into the system breaks the ability for two Firefox to talk.

your chris.ac server behaved the same way in my testing.

Yes, the Firefox clients do show: IN> {type: answer, from: 66c67960} OUT> {type: offer, to: signalin}

But there are ZERO connected peers. On my local system, restarting the node.js server and avoiding Chrome solves the problem. But basically a chrome client breaks the chat room...

chris-- commented 10 years ago

Yeah, the same happens for me. Things go wrong when the unsupported Chrome peer is selected by the bootstrap-server. We hope to get the Chrome interop working soon which would fix the problem. Until then, Chrome peers should not be allowed to connect at all.

chris-- commented 10 years ago

As it is just a matter of time, we wait until Chrome and FF DataChannel interop ships