Using Xojo.Net.HTTPSocket in a web app

Targets Web
1

I have been trying to use Xojo.Net.HTTPSocket in a web app

The Docs say “Project Types All”

Took me a little while to figure out why it’s not working.

Then I saw “HTTPSocket is not yet compatible with Web Apps.”

Will this be addressed in 2015 R3?

Thanks

Tim

2

[quote=218949:@Tim Kearns]I have been trying to use Xojo.Net.HTTPSocket in a web app

The Docs say “Project Types All”

Took me a little while to figure out why it’s not working.

Then I saw “HTTPSocket is not yet compatible with Web Apps.”

Will this be addressed in 2015 R3?

Thanks

Tim[/quote]

Not in 2015r3, sorry.

3

Tim,

Go download GlueKit https://github.com/1701software/gluekit/tree/GlueKit-for-Xojo-2015-1

The HTTPSocket there mimics the Xojo.Net.HTTPSocket class and is interchangeable. However on desktop/console/web apps it uses the old HTTPSocket internally while using the new one on iOS.

This way when it is available you can just swap it out for the real thing without any code changes.

4

GlueKit saved me on a project just today (xojo.net.httpsocket still doesn’t work fully in web apps in 2016r4.1). Can’t recommend it enough!

5

How come ?

6

Had a routine using xojo.net.httpsocket working flawlessly in a desktop app. Copied the routine into a Web app and one or more socket events didn’t fire when the socket would receive data. No error message or anything–just a silent failure.

Changed the super of the socket to the gluekit version of httpsocket and POOF! The routine worked again (just like in the desktop app) with no other changes to the code at all.

7

Since 2016R1 or so, I have been using Xojo.net.httpsocket in my Paypal listener app to post back parameters to the Paypal server in HTTP 1.1 since Xojo web does not support it. No issue whatsoever.

But I did not try to use it to get.

If you have more specific issues, you should file a bug report.