URLConnection fiasco

Christian_Schmitz · February 1, 2019, 6:44pm

You can of course just buy CURL Plugin alone and be happy.

DerkJ · February 1, 2019, 6:45pm

Still those bugs should have been solved prior a release, internal testing seems to be non existent sometimes. Customers of xojo cant test all for you, and xojo is not a startup (in which many customers expect such things to happen). As above there are 3x httpsockets each with major flaws breaking many applications suddenly. No hotfix or alternative other than go back to a previous release. Or use plugins (but that should never be necessairy.

Kem_Tekinay · February 1, 2019, 6:48pm

Disclaimer: Happiness limited to satisfaction with MBS plug-ins. General happiness not guaranteed.

DerkJ · February 1, 2019, 7:37pm

think around: if christian where a xojo employee, all would have been happy always…

Christian_Schmitz · February 1, 2019, 7:48pm

Sometimes I feel like being a Xojo employee…

But I love my freedom and as long as the community feeds me via license purchases, I dont need to apply for a real job

Julian_Mussi · February 1, 2019, 10:53pm

There are way too many socket options and the distinctions are sometimes not well documented. I’m not able to use 18R4 due to UI bugs but was surprised to the see the URL connection class.

Anyone else going a but nuts with the naming? The sockets are sometimes named for the protocol and sometimes for being secure. We have to HTTPsockets, classic and new…one being async. SSLSocket for TCP, TCPSocket and then HTTPSecureSocket that can use SSL. So now what exactly is a URL connection? Is the URL pointing to a restful API, WebSocket, XML-RPC SOAP endpoint?

I’d rather have sockets that correspond to the intended endpoint. TCP, HTTP, HTTPAsync.

Also I know christmas is over but I’d really like a websocket class for desktop.

Kem_Tekinay · February 1, 2019, 11:03pm

Ho ho ho.

Mattias_Sandström · February 2, 2019, 7:59am

FWIW I am so far having great success with URLConnection (knock on wood!) on all my targets: Windows, Mac and Linux. YMMV of course.
I am using the socket completely asynchronous in a singleton wrapper handling the logic of server communication.
The only thing I miss so far is a way to set the timeout.

Emile_Schwarz · February 2, 2019, 1:38pm

The Beatles in 1967 wrote: Its Getting Better.
Bob Dylan sings The Times They are a Changin’

Hey folks, I want to believe in The Beatles (regarless what John sings long time ago).

Andre_Kuiper · February 2, 2019, 3:30pm

All this in ONE sentence, that asks for an explanation and an example .

Paul_Rodman · February 2, 2019, 3:52pm

I did and I am.

Mattias_Sandström · February 2, 2019, 4:05pm

Will do, but for the moment I must revise my previous statement that it works on Windows.
Just filed these two bugs related to handle HTTP-headers (encoding and headers getting “stuck”):

<https://xojo.com/issue/54822>
<https://xojo.com/issue/54820>

Ivan_Tellez · February 3, 2019, 5:10am

It is sad that the “answer” is, YES it is a fiasco, just use a third party option