Separate functionality for Communication

[ms1963]

Just an idea.
I know, this is going to be a Webserver using ESP8266 and RPi Pico.
My suggestion would be to separate communication from all other functionality by introducing a separate WiFi class in charge of handling initialization, connection establishment and data transfer.
Doing this, the project would offer two benefits: providing an example for combining Pico with the ESP8266, AND,
offering a library so that others could build their own WiFi-based examples. This library could provide a simular interface such as Wireless (from pythonwifi.iwLibs) or other proven libraries.

[s60sc]

A good point, but I wrote it as an exercise - I'm still using ESP32s for my projects. Someone else is welcome to improve it, it could also be simplified as I used it to try out various concepts in the Pico SDK.

[ms1963]

I will take care of it in the next weeks. First, I need to refresh my ESP8266 skills. Michael Stal, Auenstraße 34, 80469 München Principal Key Expert Engineer, SIEMENS Editor-in-Chief, JavaSPEKTRUM Extraordinary Professor, University of Groningen

…

Am 27.02.2021 um 16:35 schrieb s60sc ***@***.***>:  A good point, but I wrote it as an exercise - I'm still using ESP32s for my projects. Someone else is welcome to improve it, it could also be simplified as I used it to try out various concepts in the Pico SDK. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.