Is there any advantage putting Xojo.Net.HTTPSockets in threads?

Targets iOS
1

In my app I use threads for data processing tasks to avoid blocking the main thread. The result is that my app is responsive even if it’s processing a chunk of data in background (and Watchdog leaves me alone).

But I’ve been wondering about my Xojo.Net.HTTPSocket based class which GETs and POSTs to our web services. As the Xojo.Net.HTTPSocket executes asynchronously, I’ve never bothered sticking it in a thread.

If I go to the trouble of executing Xojo.Net.HTTPSocket requests in a thread, will that make any difference?

2

There really isn’t.

  1. Socket events fire on the main thread.
  2. There’s a bug which prevents the events from firing when created from within a thread (forget which platform)
3

<https://xojo.com/issue/42596> Events do not fire in xojo.net.HTTPSocket on Windows when used from a Thread

4

Thanks guys.