Closed KD0NKS closed 5 months ago
Currently, callsign, passcode, filter, appId are passed in the constructor and only used in the sendLogin. Would it be more appropriate to pass these as non-defaulted parameters to the function instead? This would be a big behavioral change from perl-aprs-fap.
connection.sendLogin("N0CALL", -1, "m/500", "my-aprs-app v100")
Should send be responsible for building the packet header? Currently neither this library or perl-aprs-fap have this behavior. Ignoring my previous comment could also shorten and/or negate this.
connection.send("N0CALL", "T0CALL", ":Hello World")
Would result in the following packet being sent to the IS server:
N0CALL>T0CALL,TCIP*::Hello World\r\n
Open to re-opening at a later time. However, further work and consideration, send still requires a packet be sent with a header already constructed as the send function is also used for server commands/filter commands. This was resolved by pull request #237.
Would appreciate any feedback and discussion on this.
Should a isTransmitEnabled flag be added to ISSocket to prevent unintended sending of packets via the socket?
This would require a version bump to deprecate or remove usage of sendLine() and possibly userLogin in favor of sendLogin() and send().