Can a Node.js application running on iOS via Node.app utilize the net module for TCP/IP communication?
At the moment I don't have any Apple device to try that out myself.
Related
I'm using webpack in nodejs to create a web server, and I'm using rosbridge to interface the web server with ROS.
Is there a way that I can connect the web client on an android tablet to rosbridge (I'm running the rosbridge node on the web server machine)?
I can see the UI on the client but I don't know how to interface it with ROS on Android.
Here is the js package that I'm using, and I'm using ROSLibJS
I'm trying to implement a WebSocket server on my UWP app. Something similar to this plugin for Android and iOS, or Chrome socket server. I've looked into the Universal Windows Platform (UWP) app samples for WebSockets, but the way I understand it, it can be used as a Client side, while the Server is run separately using a PowerShell script.
My app is built with HTML and Javascript (AngularJS), compiled with Cordova framework and I wanted a WebSocket Server to run on it so that outside clients would be able to send commands to the app.
Is there any such way (or similar to it) to do this (to receive commands via TCP, etc)?
I'm tring to develop on IntelliJ 2016.2 a Web-app based on some javascript framework that runs on a spring-boot application. Now for debugging I use the Chrome Development tool (F12 on the browser). I'd like to connect my browser to the IntelliJ IDE so that I can debug directly on the IDE. Is that possible?
I installed the Chrome extention "JetBrains IDE Support", that only would a host and a port to connect (eventually some CORS option). But I'm not able to debug in the IDE. In the IDE setting, under Build, Extention, Development->Debugger I copied the port number to the extension, and I checked the can accetp external connections option. But it doesn't connect.
What exactly I have to setup on the IntelliJ side? Or Chrome side?
Txs.
I have node.js installed on Vagrant and WebStorm access to a project on shared folder via VirtualBox.
Can I run node.js application on WebStorm and see the output on WebStorm (Terminal or SSH)? At the moment I have to keep switching to Putty to run it to see the output, its gets quite tiring.
Running Node.js applications remotely is not currently supported, please follow WEB-6136 for updates.
Debugging remote applications is possible (using Node.js Remote Debug run configuration - see https://confluence.jetbrains.com/display/WI/Running+and+debugging+Node.js+application#RunninganddebuggingNode.jsapplication-DebuggingNode.jsappthatrunsremotely). But you can't see the remote process output in WebStorm console, as Stdout of it is not accessible via debug protocol WebStorm uses for remote debugging. Related feature request: WEB-17013
This feature is available through ssh on Webstorm 2017.1
Scroll down to Configuring a remote Node.js interpreter on a host accessible through SSH connection in the link below:
https://www.jetbrains.com/help/webstorm/configuring-node-js-interpreters.html
I have this web app written with express and socket.io using node.js, the app works brillantly on localhost, but when i push to my ec2 server, it connects for like 20 seconds then disconnects, and then connects again etc...
giving me the error on the node console as
warn - websocket connection invalid
info - transport end
SERVER
app = express()
server = http.createServer(app)
io = require('socket.io').listen(server)
CLIENT
socket = io.connect()
I know the problem is not with my code, because I fully tested the web app on localhost, so the only problem is where this code is running, which is my ec2 instance?
There could be many possible reasons you can get this error:
You are using browser that partially or does not support websockets. You can check if your browser supports websockets here.
Using proxy that does not support websocket. If there is some server(load balancer) between your client and your node server that does not support websocket.
You are using socket.io version 0.9.1/0.9.1-1. This behaviour is a reported bug for this version. So upgrade to latest socket.io version which is 0.9.14.
Browser connectivity is firewalled/blocked.
Code related problem.
Make sure you're using latest versions of node, express and socket.io on your ec2. Also, provide some data about currently used versions both on your local machine and on ec2 instance.
Running on your local machine you don't have to deal with network latency, NAT issues, or firewalls. Running on EC2 you have all of those.
Web Sockets are relatively new and unstable. So to begin with be sure you're running the latest versions (and let us know what they are). Perhaps the version of socket.io installed on your local machine is different than the version installed in your EC2 server.
If there is no activity during those 20 seconds before losing the connection, one possibility is that keep-alive is set too low.
See https://groups.google.com/forum/?fromgroups=#!topic/socket_io/RUv70BguZ-U for a similar problem. The solution there was to use heartbeat to keep the connection open.
A bit more on socket.io heartbeats if you're not already using them:
Advantage/disadvantage of using socketio heartbeats