WatsonTCP using delimiters

[Darby-Nelson]

Are there any examples of WatsonTCP using delimiters? Maybe I misunderstand the documentation but it seems to me that I could use WatsonTCP with a non-WatsonTCP client if they send every message with delimiters. Is that right? My client starts every message with and STX (hex 02) and ends every message with and ETX (hex 03). I don't see any way to specify what those delimiters are when setting up the server. Can anyone guide me through this process or help me see that I completely misunderstood the framing documentation?

[jchristn]

Hi @Darby-Nelson the delimiters aren't configurable but you are welcome to clone and modify to suit your needs. The framing is generally a non-pretty JSON object with metadata followed by data, separated by CRLF (see here)

[Darby-Nelson]

@jchristn - Thanks for the quick reply. Seems like this will not work for my application. Thanks for setting me straight.

[jchristn]

@Darby-Nelson of course! I have another project that might be better suited to your needs in CavemanTcp. It's built to allow people to build state machines (or their own framing) on TCP, and gives low-level stream access. Downside is of course you have to manage your own framing, but that's kind of the point of it.

Edit: you can use any TCP client with the CavemanTcp server