Is anyone actually using the new xojo.net.HTTPSocket on Windows desktop builds? If so, how are you doing it? Are you subclassing the socket or just using the socket class directly?
I cannot use it at all when subclassed, and I’ve filed a feedback and have the behavior verified from Xojo, but have no hope that it will actually be fixed any time soon. I really wanted to use the new sockets for a variety of reasons, but until they are fixed I am going to be forced to go back to the old framework sockets instead.
Unless one develops in iOS where there is no choice, I would tend to use the new framework only when it provides features not found in the classic framework.
To clarify for people here- xojo.net.HTTPSocket works fine in most Windows projects (subclassed or otherwise). This bug is really about using it from inside a Thread on a Windows desktop project.
It also doesn’t work on Windows Console or Service projects with no threading, but it did use to. Now I have to try & track down which version it did work on