• Recent
    • Tags
    • Popular
    • Register
    • Login

    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.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Serotonin TCP Persistent

    Development general discussion
    3
    4
    4.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Z
      zumiani
      last edited by

      Hello everyone.
      I'm trying to develop an easy way to read variables' values from outside Mango system.
      I have seen Serotonin TCP Persistent protocol, used by two Mango machines in order to syncronize data values between them. About this protocol I have two questions:

      1. is it open source under GPL license?
      2. is there a manual to follow to implement this protocol on custom language?

      Thankyou very much

      1 Reply Last reply Reply Quote 0
      • C
        craig
        last edited by

        http://mango.serotoninsoftware.com/downloads/mango-source-1.11.0.zip

        1 Reply Last reply Reply Quote 0
        • M
          mlohbihler
          last edited by

          The current version of "STCPP" (maybe "STP" is better?) uses serialized java objects to automatically set up points from a source instance in the target instance. Reimplementation would only be possible in another Java application (realistically speaking), and only if you included the necessary Mango classes.

          It's possible to replace the serialization with a different encoding - say JSON, XML, etc - but there are no current plans to do this.

          Best regards,
          Matthew

          1 Reply Last reply Reply Quote 0
          • First post
            Last post