mORMot Open Source

profh

Member

Registered: 2010-07-02

Posts: 161

using TSQLHttpServer under Windows server 2008

@ab,
    i used TSQLHttpServer to server as RestServer and WebSocket Server with the same port at the same time:
    1. when three or four clients connected the server, the server responsed very slow.
    2. if client posted data more than 8k, then the call.inbody at the server side will be different from the data sent by the client.
    3. when i used THttpApiServer, everything is ok.

Best Regards.

ab

Administrator

From: France

Registered: 2010-06-21

Posts: 14,661

Website

Re: using TSQLHttpServer under Windows server 2008

There is no such thing as "RestServer and WebsocketServer" in mORMot - there is a REST server over HTTP or WebSockets (once upgraded).
Please define "slow"? For which kind of requests?
Which class do you use on client side?

profh

Member

Registered: 2010-07-02

Posts: 161

Re: using TSQLHttpServer under Windows server 2008

thanks,

i have a fast and stable RestServer using THttpApiServer for years, many thanks for you for the great mORMot framework.

i am thinking about to use one server and one port(perhaps,80) to provide RestServer and Websocket functions, for Websocket is a good choice for realtime chat,but THttpApiServer can not upgrade with WebSockets, so i think about to use TSQLHttpServer.

start a server using TSQLHttpServer with RestServer and Websocket is ok, but when client access the server:
1. running c:\ab32.exe -n 2 -c 1   http://127.0.0.1/echo.htm, Time per request is 5002.999 [ms] (mean), very solw.
2. i used TSQLRestClientURI to call CallBackPut, when posted data more than 8k, then the call.inbody at the server side will be different from the data sent by the client,when posted data is just one short line,everything is ok.

Best Regards.

profh

Member

Registered: 2010-07-02

Posts: 161

Re: using TSQLHttpServer under Windows server 2008

every thing is ok whern i change TSQLHttpServer to THttpApiServer.