Greetings.
I was recently using the Telnet Driver for a customer. However I was quite surprised about the driver’s behavior.
When connecting, a message terminator can be defined. I was expecting this delimiter to be used both when sending and receiving messages. However it seems it is only used when sending: Telnet driver
What’s even worse is that apparently, telnet messages received in Tulip use no delimiter at all and are directly transferred from lower OSI layers, i.e. the received message’s content depends entirely on how the sender (and possibly intermediate devices?) split the message (probably at the TCP level?).
I think delimiter parsing would greatly simplify the received messages’ handling in Tulip. So I suggest that the Telnet Driver’s Connect action is modified to allow to choose how received messages are delimited:
- Reuse sent message terminator: self-explanatory. The terminator would be removed from the value by Tulip.
- Custom terminator: same as previous option, except a custom terminator can be defined.
- No terminator (use raw message as received): equivalent to current behavior?