If client has to struggle with different SerialPort implementations (i.e. RxTxPort and TelnetSerialPort), it's easier to use a factory which automatically decides which SerialPort implementation to use depending on the port name.
Therefore for the TelnetSerialPort an rfc2217:// URL has to be used.
This also reduces dependencies on client side code when using TelnetSerialPort.
Incorporated changes suggested in PR #77 (NRSerialPort behaviour left unchanged, means it can just handle a RxTxPort and no TelnetSerialPort).
If client has to struggle with different SerialPort implementations (i.e. RxTxPort and TelnetSerialPort), it's easier to use a factory which automatically decides which SerialPort implementation to use depending on the port name. Therefore for the TelnetSerialPort an rfc2217:// URL has to be used. This also reduces dependencies on client side code when using TelnetSerialPort. Incorporated changes suggested in PR #77 (NRSerialPort behaviour left unchanged, means it can just handle a RxTxPort and no TelnetSerialPort).