Is there a way to develop a driver such that you could send 20-40 HTTP PATCH API calls more or less in parallel (not precisely the same time but within a second or two) so that they all process more quickly compared to each command going in series after a 200OK message is received from the last command?
Is it possible for each “polling thread” to remain open in parallel so that it processes an unsolicited GET response from the API that would also be send many times at once, but with responses that match up to the individual patch commands sent previously?
Hi Michael,
The most straightforward way would be to perform the polling entirely inside a QAction but if you want to leverage the features available from a protocol then the only option that comes to my mind is to use Multi-threaded timers.
This method is typically used to perform polling on multiple IPs from the same element but it should be able to be adapted for a use case like yours.
To read more about the HTTP-specific implementation there is this subpage of the page above Multi-threaded timers – HTTP