self-propagating code

You are reading a single comment by @stevie4711 and its replies. Click here to read the full conversation.

•

ChristianW
Thanks @trezm for pointing out. Just changed that bit.

One think I'd like to improve is checking some version number before updating a remote.
Then omit the update if the version is already there or higher.

But without reading the response (not possible to receive notifications yet) this is tricky.
Some thoughts:
- just execute some verification code and let the peripheral hang up itself. Like if same or newer then disconnect(). Problem here: how can the central see the disconnect and move on? Tried it and catch() was not called. Maybe a watchdog with timeout?
- implement another service just for reading the version first. More complex and less elegant.
- waiting for a newer release so the UART response can be used.
  Other ideas?

•

stevie4711 in reply to @ChristianW

Hi @ChristianW, one idea would be to advertise the installed version number. So when scanning, the sender would skip the pucks which have the same or a higher version number. That's not completely fool proof, when two pucks are sending at the same time with different versions, the older version could in theory win. But it's better than nothing...

About

Avatar for stevie4711 @stevie4711 started