I'm looking to have a video conference website running on node.js + express.js instead of regular apache and I'm having trouble deciding on a solution.
I need the server to send the website to the user through express.js, plus, connect people in a queue so they can enter a video conference with strangers.
Should I build two different server applications, one for the express.js and one for the webRTC server, listening on different ports?
If so, how can I make the user interact with the different aplications? They will need to be able to login, be placed in the queue and be able to see the strangers once the connection is established.
WebRTC and Express.js is differ ExpressJS (Web frame work mapping your request)
but WebRTC is differ(Peer-to-Peer) communication with the help of signalling means exchange information about two browser so you can use Socket.IO or any other websocket framework
Every thing depend of signalling you want to connect particular person send signalling that particular person its not possible in Express.js so use any websocket framework like socket.io
Related
I'm trying to code a Voice-Call application using WebRTC. I know that I have to create the peer-to-peer connection to connect the two clients in order to start seeing each other in a webcam conference, BUT:
Is there any way to let the server create and maintain the connection?
Following this guide I know that one client has to offer and create a connection and the other has to "reply" in order the start a conversation.
Thank you
You will have to create socket events to send call accept/reject requests.
But first you need to setup server and client side p2p communication.
For webRTC server: Licode webRTC Server
And for ios cleint for Licode :
Visit: Licode Erizo Client iOS
This solution is the only ope source solution available on web.
Best of luck.
I was wondering how would I communicate with another NodeJS instance? For instance I have one NodeJS instance that is a chat room, how would I get the chat and all people connected to the chat from another NodeJS instance.
Secondly I was also wondering is it possible to manage Minecraft servers using NodeJS so for example create a directory copy all the necessary files then start the server with x amount of ram and be able to receive output of the server and send console commands.
You have many options, Socket.io, Rest, Soap, TCP/IP or even low-level protocols. Really depends on what is supported by Chat node. If you are the owner of both nodes, then I would suggest to use Socket.io, it is more real time and supports push-based communication, otherwise you will have to periodically hit REST or SOAP API of remote node.
As far as NodeJS is concerned it can execute shell commands for example. From there it is upto Minecraft what it offers and adheres to.
I'm creating an app where the server and the clients will run on the same local network. Is it possible to use web sockets, or rather more specifically, socket.io to have one central server and many clients that are running native apps
? The way I understand socket.io to work is that the clients read the web-pages that are served from the server but what happens when your clients become tablet devices running native apps instead of web pages in a browser?
The scenario I'm working with at the minute will have one central server containing a MEAN app and the clients (iPads) will make GET requests to the data available on the server. However, I'd also like there to be real-time functionality so if someone triggers a POST request on their iPad, the server acknowledges it and displays it in the server's client-side. The iPad apps will (ideally) be running native phonegap applications rather than accessing 192.168.1.1:9000 from their browser.
Is this technically possible to connect to the socket server from the native apps or would the devices have to send POST requests to a central server that's constantly listening for new 'messages'? I'm totally new to the whole real-time stuff so I'm just trying to wrap my head around it all.
Apologies if this isn't totally clear, it's a bit hard to describe with just text but I think you get the idea?
Correct me if I am wrong.
You have multiple iPads running native app. They send a POST request to your node JS server which is running in a computer in the same local network. Whenever the server receives a request from app, you want to display that a request has been received in your computer screen.
If my assumptions about the scenario is correct, then it is fairly easy to do. Here are the steps to do it.
Create a small webpage (front end). Load socket IO in the front end page like this -
<script type="text/javascript" src="YOUR_SERVER_IP/socket.io/socket.io.js"></script>
Then connect to server using var socket = io(). This should trigger connection event in your backend.
Handle all POST request from apps normally. Nothing special. Just add a small snippet in between. socket.emit('new_request', request_data). This sends new_request event to front end.
Handle the new_request in your front end using socket.on('new_request', function(request_data) { ... });. That's it. No need to add anything to your native app for realtime update.
The second step would be a little complicated as it is necessary to make socket variable available inside all POST requests. Since you chose node.js, I don't think you need any help with that.
Not totally clear on your project, but I'll try to give you some pointers.
An effective way to send data between native apps and a server is using a REST server. REST is based on HTTP requests and allows you to modify data on the server, which can connect to your database. The data returned is typically either JSON or XML formatted. See here for a brief intro: http://www.infoq.com/articles/rest-introduction
Android/iOS/etc have built in APIs for making HTTP requests. Your native app would send a request to the server, parse the response, and update your native UI accordingly. The same server can be used from a website using jQuery ajax HTTP requests.
Express.js is more suited to serving web pages and includes things like templating. Look into "restify" (see here: mcavage.me/node-restify/) if you just want to have a REST server that handles requests. Both run on top of node.js (nodejs.org).
As far as real-time communication, if you're developing for iOS look into APNS (Apple Push Notification Service). Apple maintains a persistent connection, and by going through their servers you can easily send messages to your app. The equivalent of this on Android is GCM (Google Cloud Messaging).
You can also do sockets directly if that's easier for you. Be careful with maintaining an open socket on a mobile device though, it can be a huge battery drain. Here's a library for connecting ObjC to Socket.IO using websockets, it may be useful for you: https://github.com/pkyeck/socket.IO-objc
Hope that helps!
To answer your question, it is definitely possible. Socket.io would serve as the central server that can essentially emit messages to all of the client. You can also make Socket.io listen for the messages from any of the clients and serve the emitted message to the rest of the clients.
Here's an example of how socket.io can be used. Simply clone, npm install, and run using 'node app.js'
All you have to do is to provide a valid server address when you connect your socket from the iPad clients:
var socket = io.connect( 'http://my.external.nodejs.server' );
Let us know if you need help with actual sending/receiving of socket events.
It is possible to connect to Websockets from your apps.
If you are using PhoneGap then you need a pluging that gives support to websockets in your app (the client) and then use websocket like normal way using Javascript see this.
If your app is native iOS look into this it could help you.
The primary use of the Sockets in your case is to be a bidirectional "pipe" between an app and server. There is no need of server sending the whole web-page to the native app. All what you need is to send some data from server to the client(app) in response to POST (or GET) request and then using this data on client side to update client's UI in real-time. If you are going to use moderate amount of devices (say tens of them), you may have connected all of them to the server permanently keeping individual socket connection open for every individual link server-to-app. Thus you may deliver data and update client's state in real time.
In fact web browsers also employ sockets to communicate to web servers. However as in general case there is no control on amount of concurrent clients in Internet, for the sake of limited networking resources conservation, servers do not keep sockets open for a long time, closing it just after the web-page was sent to client (or timeout has expired). That's how HTTP protocol works on the low level. The server waiting for the HTTP clients (browsers) by listening the 80 port, responding them by sending the whole web page content, then closing the connection and keep waiting for another requests on the same port.
In your case it's basically a good idea to use socket.io as it's a uniform implementation of sockets (ok WebSockets) on both client and server side. The good starting point is here
i have created an notification server, which is application specific, now am preparing an application independent server to send notification to the clients using that application for synchronizing purpose, am not asking code and all, will you give me suggestion on this.
What is the basic need for an development of application independent component?
The best thing to do is to create a message queue (pub-sub) that different applications can connect to easily.
If your app isn't that big you can create a TCP server and send information to everybody connected. If you need to scale your app you can use something like Redis, ZeroMQ, RabbitMQ etc.
You can checkout my Twitter Steam application to see how I achieve that:
app: https://github.com/alessioalex/Presentations/tree/master/WebUp4/applications
TCP Server implementation: https://github.com/alessioalex/Presentations/blob/master/WebUp4/applications/twitter-streaming/tweetBroadcaster.coffee
I don't quite know how to search this in google:
"client to client websocket connections"
"browser to browser websockets"
"websockets without a server"
Haha, is there a way for someone on a webpage in the browser to communicate directly to another person on a web page in the browser, without touching the server?
I am very familiar with socket.io, but that requires all clients emit messages to the server, which can broadcast them to the other connected clients. I am not familiar with the details of web sockets though, so maybe there's a way to communicate without sending messages through the server.
Is this possible? I just want to know the scope of web socket functionality, the limits you can take them too, etc.
Not Web Sockets, but four years later and now we've got browser-to-browser communication!
http://www.webrtc.org/
There are JS libraries built around it to make it easier (e.g. https://simplewebrtc.com/). However, it does still require a server to orchestrate connections.
I know this question is ancient, but it showed up in Google when I searched so it likely will for others!
This is not possible, you have to have the server in the middle.
For an application to accept connections, it has to have a server port open and listening for incoming requests. You cannot have a server socket exposed from a browser. I dont know if you can expose a server socket from within an applet. But even if you could, you would need to know the IP address of the other client for establishing a peer to peer connection.
Well, technically when you broadcast, the client emits to the server, the server broadcasts to everyone. I don't think with the current architecture of the web peer to peer connections like this is possible.
But it is possible that a client send a message to server specifying another client ID, and the server sending it to the other clients using sessions.
The moment you have a client listening for websockets (which you have to do in other to communicate), it becomes a server.