Interface base service execute long time response error

xchinjo · 2017-04-02 10:56:47

TInterfacedObjectFakeClient.FakeCall(IRemoteSQL.Execute) failed: 'URI root/RemoteSQL.Execute/4
returned status 'Invalid Request' (501 - Server not reachable or broken connection)'.

ab · 2017-04-02 15:12:20

This is as defined.

You can enhance the timeouts on client side.
Or, even better, change your SQL request to use paging and return less information.

xchinjo · 2017-04-02 15:15:25

how to enhance the timeouts on client side.
or client side can do callback function?

Last edited by xchinjo (2017-04-02 15:26:16)

ab · 2017-04-02 17:39:20

IMHO the best design, for a mORMot client, is to use a callback interface to notify when the work is finished.
See https://synopse.info/files/html/Synopse … l#TITL_152

Otherwise you can change the timeouts in the constructor Create() method of the HTTP client class.

xchinjo · 2017-04-03 00:25:25

thank you.

mORMot Open Source

#1 2017-04-02 10:56:47

Interface base service execute long time response error

#2 2017-04-02 15:12:20

Re: Interface base service execute long time response error

#3 2017-04-02 15:15:25

Re: Interface base service execute long time response error

#4 2017-04-02 17:39:20

Re: Interface base service execute long time response error

#5 2017-04-03 00:25:25

Re: Interface base service execute long time response error

Board footer