Do not implement any TCP transport. Use http and nginx as reverse proxy in front of the node as a load balancer. Dont invent the wheel in other words.
On Friday, February 5, 2016 at 5:38:32 AM UTC+2, Dieter Stubler wrote: > > Hi, > > Currently we have an old style web frontend to our schedulix Open Source > Enterprise Scheduling System. > > I'm thinking about to use nodejs as backend for our redesigned SPA GUI. > > What i need is a webservice which will run on nodejs serving as a command > executor of schedulix statements on our server backend. > The webservice should get statement, hostname and port of our backend as > well as username and password. > to connect to the scheduling server via tcp to execute the command > retrieve the rsesults and give it back to the SPA. > > The question is not how to do socket io and json etc. > > I just need a starting point or a hint to a resource example or sometjing > else showing me how to implement a webservice in general. > > Sorry if the question is quite silly but googling didn't helped me out so > far. > > Regards > Dieter > -- 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/d55b18b1-65c7-43ad-83e6-601f990fe749%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
