On Oct 13, 2014, at 11:00 AM, Rene Ummels <[email protected]> wrote:
> Hi Aria, > > Let me shortly explain what I try to achieve: > A client connects to our application, a TCP connection is then set up and > kept open. At some point in time the client sends data to the application; > this triggers the > application to update the database and also to send new data > (binary/JSON/MQTT) back to the client. > Later on in our project we will change from TCP to HTTP-REST. > Do you need more info? > > Do I understand correctly that you for instance propose to design a Proxy in > our Application Server and that this Proxy connects to external node > containing the Node.js application? > That is one option. Not a bad one if the java application is not legacy. I think I would probably make node the outer layer -- write a TCP protocol handler with node, and have it pass data to the existing application. Start building REST API using node. But I have a strong bias for doing things in node. I would probably not integrate node with the application server -- I would deploy using ndm or forever or pm2 -- and just run the app next to Java, not inside or started by it. Are there deployment constraints you're trying to work around? -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/C4C224F3-949E-41A0-B52F-87322EFBCAAD%40nbtsc.org. For more options, visit https://groups.google.com/d/optout.
