New MicroPython implementation of uasyncio (WIP)

[amotl]

Dear Jean-Christophe,

as I just found [1] being conceived these days, I found it worth to notice you about it. There might be a chance MicroWebSrv3 could be based on it in the future.

With kind regards,
Andreas.

[1] micropython/micropython#5332

[jczic]

MicroWebSrv3 or XAsyncSockets? :')
(I've also a very light multi-workers lib: https://github.com/jczic/MicroWorkers)

[amotl]

MicroWebSrv3 or XAsyncSockets? :')

Probably XAsyncSockets ;].

I've also a very light multi-workers lib: https://github.com/jczic/MicroWorkers

Thanks. Both will be able to profit from the real asyncio implementation in terms of memory efficiency and maybe also performance.

[jczic]

Yes, but the objective is indeed to make both parallelism and concurrency like XAsyncSockets.
I agree for the use of asyncio in native, today XAsyncSockets can however have 1000 active TCP connections managed on a pool of 50 threads for example.
With CPython, this is very great :)

[buzzware]

The features of this project sound great, however for my ESP32 project, with light control and http polling (as a client) on a Pycom LoPy4, I'm not sure if I can use this because it seems to be thread based. I want to be able to control hardware by a HTTP API - will this library cause problems by threading? I'd be more comfortable if it was uasyncio based, but I know I don't know enough to be sure.
Are there potential integration problems with hardware or other libraries due to this library being thread based?

[buzzware]

Here is a working proof of concept for u/asyncio support https://github.com/buzzware/MicroWebSrv2