I have some socket-io server on node.js running.
I want to communicate from Windows Phone application to this node.js.
But I have no idea how to start with this.
I've found SocketIO4NET and it's running fantastic but on console application. I can not move it to Windows Phone unfortenately because there is no WP version of SocketIO4NET assembly.
Does anybody have any idea how to bite it?
One approach to this could be as follows.
Create a phonegap app for the Windows Phone, with socket.io.js included in the app (so that it can send events to the node server). And obviously create a NodeJs server, with socket.io module, which will listen and respond to the events sent from the phonegap app.
This approach could be useful, if you really don't want to stick to a native Windows Phone app.
Refer to this video to get a clue. http://www.youtube.com/watch?v=M5IAlnU96SI
Related
I created a firebase project. This communicates with a mobile application (node.js). As part of this project I want to use pupeeteer.
I have no problem launching functions using pupeeteer in firebase.
The problem is that I want to make the user perform actions. So I have to display the web page (pupeeteer) in the application via a browser generated by the server (with a firebase function?)?
However I have no idea how to launch a browser instance in the background and close it at the end of processing?
Can you help me ? Is this the right solution?
I want to use this :
This library does 2 things:
Download the chromium binaries and launch a Chromium process.
Connect to this process with Websocket and send json commands to control the browser.
Due to limitations on mobile platforms (iOS and Android), it is not possible to launch an external Chromium process on iOS and Android. So, step 1) does not work on mobile.
You can still use puppeteer-dart on Flutter either with:
Flutter on Desktop (macOS, windows, Linux)
Flutter on mobile BUT with the actual Chrome instance running on a server and accessed from the mobile app using puppeteer.connect
The pub.dev website reports that this library works with Android and iOS. The supported platform list is detected automatically and can't be manually modified to express the current limitations
We have an Electron app that comes bundled with a .NET core application.
These two applications need to be able to communicate, right now we use ancient technology by writing to a JSON file that the .NET core application "polls" from regularly.
We want to upgrade this to use sockets instead. The NodeJS developer want to use socket.io and the .NET Core developer wants to use SignalR.
So the questions are probably:
Does SignalR run fine with Node?
Does Socket.io run fine with .NET Core?
Should we just use standard WebSockets on both ends instead?
SignalR can be running on Electron as Client.
Socket.io is hard to communicate with .net.
(Recommended) SignalR on both sides(.net as Host, Electron as client)
Microsoft docs : Running SignalR Javascript client
or using websocket protocol in both-side.
As you know Socket.io is a library which implements websocket. so SinalR and Socket.io is not fully matched on each other.
socketio4net(socket.io client on .net) is not maintained now.
So if you want to communicated by socket.io,
You can running socket.io on Electron as Host, and .net as client with WebsocketPackages (not SignalR)
I am developing a small project which contains few applications:
A node.js rest API
A node.js app that use socket.io.
A static app that server html js file to the client.
I am also using a MongoDb.
In few weeks, I'll have to deploy this app in production and I have some requirements that the app should be installed on windows and Linux server (Don't really know if it really matters).
I had a look at some tooling :
StrongLoop Process Manager
PM2
Forever
But cannot really find out if these tools are up to date or if there are better alternative in 2016 ?
Here are what seem to be the recommended ways that I've found:
Windows: iis-node (and this vid is helpful to get that going). Also note you'll need IIS 8x to support websockets.
Linux: PM2 to manage the process, and nginx for proxy server. This article has helpful step-by-step for Ubuntu.
I want to write android chat based application.
So intead of using gcm I want to extend the existing xmpp server.
So i tried with xmpp node js server. But all the features are not implemented in that server .So i thought extending the nodejs xmpp server.
Are they any better docs or tutorials to understand more about xmpp server.
if not nodejs xmpp server, how can i extend jabber or any other xmpp server.
I googled a lot but I didn't find any docs related to extending a jabber-like server.
You can use Openfire server source code from Github:
https://github.com/igniterealtime/Openfire
You can build openfire source in IntelliJ if you are already familiar with Android Studio. Here is some insight:
https://discourse.igniterealtime.org/t/can-i-develop-openfire-using-ide-tool-intellij-idea/76503
Also you can open Openfire source code in Eclipse:
Setup Eclipse for OpenFire server
I´m developing a Windows 8 App, and it needs a desktop app running on background to work properly.
So i have two questions:
1.- The OS is a Windows 8.1 Industry Embedded. I need to autorun the desktop app and my Windows 8 app at startup.
Here explains how to do so with a Windows 8 App, but not with a desktop app, so i´m using this other solution to add the application to the Windows Startup folder, but i´m not sure if this is the best way.
2.- Then, when my app starts, i should check if the other app is running or not to work in one way or another. How can i check that? I´m developing with HTML and Javascript.
Thanks!
Yes that is the 'proper' solution to starting a desktop app on startup. Otherwise you can look at creating a windows service that manages the app lifecycle.
By design, winRT apps are not supposed to talk to desktop applications, but if you are sideloading the winRT app (i.e., not through the Windows Store), you could run a local server with your desktop app, and then enable local loopback with localhost in your winRT app and communicate that way.