Hello Ak, I’m trying to get socket object from:
“development/openLuup/io.lua”, line 491
to “development/openLuup/requests.lua”, line 787
Please, would you show workarounds to get that socket-object and make scheduler.socket_unwatch() for it in “requests” code? or, if not, maybe, would it be possible to discuss the possibility to provide patch to openLuup that will expose altUI<–>luup sockets" to “openLuup/requests.lua” code (so it will be possible to take control on socket). I can write a patch.
I just need to know for now, if such a patch be acceptable ideologically to the project.
This will allow to provide continuous/delayed response sending for luup requests but to avoid complex “async_send” mechanisms or openLuup-core major modification.