You are not logged in.
Pages: 1
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
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.
Online
the websocket client suffered some Hung up problem
Offline
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
Pages: 1