HTTPSocket in a thread?

I’m confused about threads.
I know we cannot update UI from a thread, and to be honest, I havent used one before.

Part of my app ‘calls home’ for registration.
When that happens, I use a synchronous HTPSocket call, with a timeout
If that timeout is long and the user has no or a slow internet connection, everything stops for a while.

So: is this a useful place to try a Thread?
Can I make this call in a thread and keep the UI responsive while we wait for an answer from a web site?

Any pointers/tips?

Instead of using a thread, use the HTTPSocket in asynchronous mode. That will keep the UI responsive, and is much simpler to implement.

Use HTTPSocket.Yield = True

Does that mean I need to create a property and add code to a ‘completed’ event or similar?
Until now I have called directly with mysocket.get( param, duration)

[quote=279977:@Jeff Tullin]Does that mean I need to create a property and add code to a ‘completed’ event or similar?
Until now I have called directly with mysocket.get( param, duration)[/quote]

Indeed Asynchronous requires the use of the completed event. But then it is like if the HTTPSocket had its own thread.

Or use HTTPSocket.Yield as advised by Ashot.

I’ll give these a try. Thanks guys