Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Persistent TCP listener
-
We have a number of MangoES units connecting back to a central Mango server and using the Persistent TCP module to transmit and sync data.
Some stations transmit realtime data and some just do a periodic sync, which is configured as per the publisher on each site. At the moment I have been configuring a separate listener (listening on a different TCP port) for each site.
Just doing a bit of a review of how this is set up and have the following questions:
-
Is it best practice to create a separate data source listener for each MangoES and if so, would each separate listener then need to listen on a different port?
-
Is is there any risk or reason not to have multiple stations sending data to the same listener?
Thanks!
-
-
Jeremy,
We usually create one Data Source ('listener') for each Publisher. This can make life a lot easier if you have to debug one of the connections and end up turning on the logging. I don't recall ever having 2 Persistent Publishers connect to one Data Source, but in theory its possible.
-
Hi Terry
It is definitely possible to have one listener receiving data from mulitiple publishers, I have done this by accident a few times :-}
Do you know whether I can have multiple listeners configured and all using the same port? Would that be recommended? I would like to avoid having too many ports open.
Kind regards
