This seems like a bug, or is at least astonishing.

The TCP channel for the External Editor API seems to close after each message is sent. I find this astonishing. I would expect I could send:
Code:
{"messageID":3, ... } \n
{"messageID":3, ... } \n
{"messageID":3, ... } \n
keeping the connection open for each message, but it seems as soon as TTS sees the closing parend of the message body, it then closes the channel entirely and ignores anything past.

Is there a reason for this? Is this intended?

I probably wouldn't care if I weren't trying to do significant automation, but at least on Windows, I'm running into port exhaustion and it's not clear to me why this needs to be implemented this way. For now I'm looking into some flow control, but that slows down my automation pretty quickly.