The Xojo Socket control seems to have a lot of issues. What is everybody else doing to work around this? MBS? In case anyone stumbles upon this, or it gets indexed by the web, I’m going to post this here. It’s a perplexity search for the exact issue, and I’d like it to be public, and I know that …

I feel for you. Only choice is to stop using Xojo… It’s really hopeless.

Comparing to Java it is simple only one thing: crap. I think that somebody writing an application in the need of sockets should be aware of this and change to C# or Java. For Web applications and especially backends it is no solution to use Xojo.

Thank you. That was amazingly helpful.

If you’re still using Xojo.Net.HTTPSocket , or HTTPSecureSocket, switch to URLConnection - its a much more direct mapping to the OS provided services all around In the apps where I’ve used URLConnection its been reliable Never had it get to be unresponsive We switched away from HTTP Socket as it …

[image] jay: Thank you. That was amazingly helpful You keep going round and round with Xojo. It’s not going to stop happening until you take action. What would it take for you to give up on Xojo?

If Not Nil

Xojo Socket Control

Xojo

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled