Home Forums Support Communication with NODE.JS SERVER (Socket.io features)

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #3020
    Anonymous
    Inactive

    First does your library support Web Sockets / Socket IO?

    Two, I created a demo app using the UnmanagedConnection sample, that was successfully able to get a two way communication with a Node.JS Server.

    Unfortunately, this only works when the node.js server is initiallizet with server = requires(‘net’), meaning a raw TCP streaming end point.

    My problem is, ours is a Http/Https server , meaning server = require(‘http’), with an initialization of io = require(‘socket.io’).listen(server). That means the library

    My question is, does your library support and do you have any samples of it supporting communication with a http/https endpoint? I would like to connect to an endpoint like IPTools.ParseEndPointFromString(“https://10.10.200.3:443”);

    I already bought this library for this purpose and do not want to waste any more time trying this feature if it is not supported

    #3022
    Anonymous
    Inactive

    For managed connections our library implements it’s own protocol to provide generalised, high speed, network throughout, while providing a much wider variety of common connection features than most other protocols. We added support for unmanaged connections in version 3.0 so that people could implement their own protocols if they wish.

    Given there is an enormous number of protocols out there we could never hope to implement even a fraction of them. We have been investigating the possibility of implemented some of the most common but we just haven’t had the demand for it to date.

    Web Socket’s‘s a specific protocol defined in rfc6455 for which we do not currently provide an implementation, although the vast majority of what you would require if you wanted to add this support to NetworkComms.Net is already in place. All you would have to do is write a parser that sits on top of your unmanaged connection that correctly interprets incoming byte[] from websocket peers. If you did create this implementation and donated it to NetworkComms.Net we would offer you a 100% rebate.

    If you do not want to do this however you are still entitled to a full refund within 30 days of purchasing if you do not continue to use the library.

    Kind regards,
    Marc

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.