-
Notifications
You must be signed in to change notification settings - Fork 285
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
Too fancy! #1
Comments
Hi dennis Hey, A couple friends and I built a multi-user webrtc demo, You can have a look at the demo on http://multiwebrtc.nodejitsu.com/ and if you want to see the code for the site, you can find it here https://github.com/dennismartensson/webrtc.io-demo For the client: https://github.com/sarenji/webrtc.io-client for the server: https://github.com/cavedweller/webRTC.io let us know what you think, Dennis |
Hi, You have to have node installed and npm and the dependencies , There are now updated instructions at https://github.com/cavedweller/webRTC.io on how you go about setting it up. /Dennis |
hi Denis! I am using CentOS 5.5 32 bit. What can i do with the client and server code for it's working? Please explain more detail. |
Hi Ronal, The setup proces did become a lot essayer with yesterdays updates. So I do recommend you to start over. So here is a step by step guid on how to get the demo to work, Run in your terminal
Ïn a version of Chrome that have webRTC support. open localhost:8000 in Chrome click allow to see your camera open localhost:8000 in Chrome click allow to see your camera and the connection will be made between your to open windows. I do hope that this make it clearer and that you get it to work, I am not sure I do understand your example? "Example, user A use a Chrome Canary connect to the web server, user B is does the same to the web server by client js code and the js code of server in the middle to connecting 2 user, A and B." /Dennis |
Hi, Have you done github's setup with keys for connecting? /Dennis |
hi Denis, Can u help me! Ronal. |
You have to be in the same room, So go to http://localhost:8000/#1 in to browser windows. Are your problems with git clone and error on the socker.io module resolved? /Dennis |
hi Denis, Can you help me this prolem? Ronal But
Viên Nguyễn |
Hi, I cant tell whats the problem you are having because I have tested the setup multiple times on different machins and it works fine. I do not know where your "partner" is but localhost can only be used on your local matchin. If you want to use the demo on different networks and are not planing to do any developing with the library, I sugest that you use the demo site. If you are planing on doing developing with webRTC.io and have not done node.js stuff before I sugest that you start to learn about that on some easier typ of app then a webRTC app. To understand webRTC and how it works I sugest that you look at http://www.webrtc.org/ and for node.js I sugest that you start with http://www.youtube.com/watch?v=jo_B4LTHi3I and try to do the example he is creating, I do have a project going where I have same screen cast talking about realtime web. I will try to do one on webRTC.io later this week but you can start at the first movie if you like to learn about realtime web and are not so use to it. You will find the movies at http://dennismartensson.com/ I hope that this answer will help you out /Dennis |
hi Denis, Thank you! |
hi Denis, [root@TLS example]# node server.js Thank you! On Mon, Aug 6, 2012 at 10:39 PM, Dennis <
Viên Nguyễn |
Hi Ronal, Have you enabled WebRTC in about:flags on Google Chrome Canary? If not, please follow the instructions here: http://www.webrtc.org/running-the-demos#TOC-Media-Stream-and-Peer-Connection-Flags- David |
Hi Denis, BR, On Tue, Aug 7, 2012 at 10:51 AM, David Peter notifications@github.comwrote:
Viên Nguyễn |
Hi Denis,
Thanks! |
Have a lock at me answer here webRTC-io/webrtc.io-client#3 You can also read me explaining this in the google groupe https://groups.google.com/forum/?fromgroups=&hl=sv#!topic/discuss-webrtc/26UNDNm-q0w /Dennis |
:P
The text was updated successfully, but these errors were encountered: