#1 2018-03-29 14:11:43

pvn0
Member
From: Slovenia
Registered: 2018-02-12
Posts: 210

question about TSQLHttpClientWinSock

HTTP client(s)

documentation wrote:

As stated above, there is still a potential performance issue to use the direct TSQLHttpClientWinSock class over a network. It has been reported on our forum, and root cause was not identified yet.

Does the forum thread about this still exist? I couldn't find it in search. I want to use websockets because of the callbacks which are just awesome btw and just want to know more about this problem if it still exists.
Thanks!

Offline

#2 2018-03-29 14:23:44

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,203
Website

Re: question about TSQLHttpClientWinSock

I guess this is a very old feedback, from old implementation.
A lot has been modified and tuned in SynCrtSock since.
We currently see no performance problem using it, even on cross-platform - but behind a nginx reverse proxy, for safety.

Offline

#3 2018-05-24 00:47:21

keinn
Member
Registered: 2014-10-20
Posts: 100

Re: question about TSQLHttpClientWinSock

the websocket client suffered some Hung up problem

Offline

#4 2018-05-24 07:29:24

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,203
Website

Re: question about TSQLHttpClientWinSock

What is an "hung up" problem?

Offline

#5 2018-05-24 14:38:43

keinn
Member
Registered: 2014-10-20
Posts: 100

Re: question about TSQLHttpClientWinSock

i mean, i suffered "client not response" issue, when using the TSQLHttpClientWebsockets。 
when the client callback deal with long time process, it will block the websocket connection.
detailed here: https://synopse.info/forum/viewtopic.php?id=4547
is there a way to post the callback process to a dedicated backgroud thread? other than Client.ServiceNotificationMethodViaMessages()?,
sometimes there is no window form to process Tmessage loop.

Offline

Board footer

Powered by FluxBB