Changing priority of task about asynctcp HOT 4 CLOSED

It runs at 3 so it has a higher priority than the loop() method. It should have no impact on your code as long as you don't abuse the callbacks (ie run something that isn't directly related to sending/receiving data)

from asynctcp.

I work with shit registers and need to switch their state as fast as possible. This is done directly in the software via switching a PIN state from HIGH to LOW and vice versa. And setting the priority to 1 fixed the issue that request handling had an effect on the switching times. And the requests are still handled perfectly.

from asynctcp.

[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

from asynctcp.

[STALE_DEL] This stale issue has been automatically closed. Thank you for your contributions.

from asynctcp.