Presently, remotesd likes to continuously send a "MEGA65FT1.0" string over the serial comms. Seems like the sole intention behind this is in order for any future mega65_ftp process that starts up, it can check the serial traffic to see if such a string is there, and then conclude that remotesd is presently running on the m65-hardware (hence it doesn't need to upload it there again).
Having all this constant serial comms traffic is quite a nuisance when you want to debug the serial traffic between mega65_ftp and remotesd though, and I'd rather things weren't so spammy, so that I can concentrate on the details of the genuine traffic that I do want to debug.
Note that it also renders matrix-mode unusable as a debugger too, as all these "MEGA65FT1.0" strings are constantly printed there too.
Was thinking, at some stage, instead of remotesd-side constantly sending that "mega65ft1.0" string on the serial comms, perhaps this alternative approach would be less spammy in future.
Since mega65_ftp seems to be the only recipient that is interested in this string, then:
mega65_ftp could instead make a 'request' of remotesd, "Hey remotesd, what is your version?"
If remotesd is still running, it will see this and respond, "my version is mega65ft1.0"
If mega65_ftp doesn't get any response, it can conclude that remotesd is not presently running.
Anyways, will consider that approach another time.
gurcei
commented
3 years ago
Presently, remotesd likes to continuously send a "MEGA65FT1.0" string over the serial comms. Seems like the sole intention behind this is in order for any future mega65_ftp process that starts up, it can check the serial traffic to see if such a string is there, and then conclude that remotesd is presently running on the m65-hardware (hence it doesn't need to upload it there again).
Having all this constant serial comms traffic is quite a nuisance when you want to debug the serial traffic between mega65_ftp and remotesd though, and I'd rather things weren't so spammy, so that I can concentrate on the details of the genuine traffic that I do want to debug.
Note that it also renders matrix-mode unusable as a debugger too, as all these "MEGA65FT1.0" strings are constantly printed there too.
Was thinking, at some stage, instead of remotesd-side constantly sending that "mega65ft1.0" string on the serial comms, perhaps this alternative approach would be less spammy in future.
Since mega65_ftp seems to be the only recipient that is interested in this string, then:
Anyways, will consider that approach another time.