Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sample Socket.io Server #10

Open
dodolboks opened this issue Apr 1, 2013 · 8 comments
Open

Sample Socket.io Server #10

dodolboks opened this issue Apr 1, 2013 · 8 comments

Comments

@dodolboks
Copy link

Hii Muaz, can you add sample Socket.io Server in this repository ? i try [1] with my python socket.io server but its not work.

My python Code

https://gist.github.com/dodolboks/5284171

[1] https://googledrive.com/host/0B6GWd_dUUTT8RzVSRVU2MlIxcm8/webrtc-broadcasting/

Thanks

@muaz-khan
Copy link
Owner

See the list of socket.io server implementations for python. I'll try to add some wiki-pages soon to explain installation steps; especially for node.js

@dodolboks
Copy link
Author

+1 for node. its easy convert to python/gevent-socket.io. thanks muaz.

@saada
Copy link

saada commented Apr 9, 2013

👍

@JamieMcDonnell
Copy link

Hi Muaz, glad I found this thread, as I contacted you by email for this one. +1 for a sample node socket.io server if possible please? And any ideas why interop between FF & Chrome is not functioning at the moment?
Cheers, nice work man!
Jamie

@muaz-khan
Copy link
Owner

Firefox-to-Chrome streaming is continuously working (all the time); however Chrome-to-Firefox started failing out of a known bug which is fixed and landed in latest canary. Bug was:

The numeric value of the session id and version in the o line MUST be representable with a 64 bit signed integer. It looks like chrome is making a 64bit unsigned int. The Mozilla bug about this is here.

My video conferencing experiments needs something like dynamic namespaces generated/handled by socket.io. I'll create a separate repository for WebRTC signaling gateway implementations. I'm thinking to include custom SIP implementation there too (in a few weeks).

If you're using socket.io over node.js: you can link this file:

<script src="http://webrtc-experiment.appspot.com/socket.io.js"></script>

@JamieMcDonnell
Copy link

Hi Muaz,
thanks once again for your prompt reply - I am testing now in Chrome Canary
to check the bug is fixed.

Does this file start the messaging server as well? Or is this the straight
socket.io? I have socket.io running locally, but the server I am running is
custom for our app and will take a bit of work to re-write.

Thanks, and kind regards

Jamie

On 25 April 2013 04:07, Muaz Khan [email protected] wrote:

Firefox-to-Chrome streaming is continuously working (all the time);
however Chrome-to-Firefox started failing out of a known bughttps://code.google.com/p/webrtc/issues/detail?id=1628which is fixed and landed in latest canary. Bug was:

The numeric value of the session id and version in the o line MUST be
representable with a 64 bit signed integer. It looks like chrome is making
a 64bit unsigned int. The Mozilla bug about this is herehttps://bugzilla.mozilla.org/show_bug.cgi?id=859303.

My video conferencing experiments needs something like *dynamic namespaces

  • generated/handled by socket.io. I'll create a separate repository for
    WebRTC signaling gateway implementations. I'm thinking to include custom
    SIP implementation there too (in a few weeks).

If you're using socket.io over node.js: you can link this file:

<script src="http://webrtc-experiment.appspot.com/socket.io.js"></script>


Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-16985030
.


Jamie McDonnell
Digital design in all shapes and sizes
ui-ux-design.com
skype: jamie.mcdonnell

tel. +420 725 871 729

AVG.com - Ultimate protection for everything you do online
Become an AVG Fan at: http://www.facebook.com/avgfree?ref=ts
Get the latest news at: http://twitter.com/officialAVGnews
Keep on top of the latest AVG news and gossip at :

http://blogs.avg.com/gb-en/blogs

360 Cities - Your World in Immersive Reality
www.360cities.net
blog.360cities.net
facebook.com/360cities

twitter.com/360cities

@muaz-khan
Copy link
Owner

socket.io over node.js added. Demo — with 3-to-5 lines of changes: it must work in all WebRTC Experiments.

@JamieMcDonnell
Copy link

Wonderful, thanks for letting me know Muaz.
Regards
Jamie

On 28 April 2013 14:53, Muaz Khan [email protected] wrote:

socket.io over node.jshttps://github.com/muaz-khan/WebRTC-Experiment/tree/master/socketio-over-nodejsadded.
Demo http://webrtc-signaling.jit.su/ — with 3-to-5 lines of changeshttps://github.com/muaz-khan/WebRTC-Experiment/tree/master/socketio-over-nodejs#are-you-want-to-use-same-socketio-implementation-for-other-webrtc-experiments:
it must work in all WebRTC Experimentshttps://webrtc-experiment.appspot.com/
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-17133591
.


Jamie McDonnell
Digital design in all shapes and sizes
ui-ux-design.com
skype: jamie.mcdonnell

tel. +420 725 871 729

AVG.com - Ultimate protection for everything you do online
Become an AVG Fan at: http://www.facebook.com/avgfree?ref=ts
Get the latest news at: http://twitter.com/officialAVGnews
Keep on top of the latest AVG news and gossip at :

http://blogs.avg.com/gb-en/blogs

360 Cities - Your World in Immersive Reality
www.360cities.net
blog.360cities.net
facebook.com/360cities

twitter.com/360cities

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants