Difference between tcp/3037 and other ports?

Question

Not sure if this is a bug or intentional behaviour? 
 I have configured TCP port 3555 in the UI as a TCP Server Port 
 When using TCP port 3037 to connect to Eos, the rate of received /eos/out/active/cue/text messages is far higher than when I connect using port 3555. That is 3037 provides a data stream that is easily used as a more-or-less realtime cue progress indication, but 3555 does not. 
 Secondly, I've have a couple of macros which take the form Send_String /rhl/action, and cues with a Send String in Execute parameters and when I connect over port 3555 these are received as expected, but connected over port 3037 these messages are not received.

Matt Pumplin · Answer

TCP ports other than the ones for mobileRFR and Third Party RFR refresh at ~1 message per second. That's true for arbitrary ones that users select (like your 3555) as well as port 3032. 
 The Third Party Port 3037 refreshes much faster to support closer-to-realtime feedback of cue progress, etc. 
 This Support Article appears to be out of date, so I'll fix that. OSC Output Refresh Rate - Electronic Theatre Controls Inc 
 I'll also add a bit more to TCP port for OSC communication with Eos Software - Electronic Theatre Controls Inc