Monte and Tom,
Yes, that is true. The client will wait for a while. It can still drop
though if for any reason the socket disconnects while waiting for an answer
(IIRC).
A good practice, is to cache and pre-process aggressively so that you need
to minimal work when the request actually arrives. I
Ok..so the problem was that in my request processing, I was outputting
certain data into the message box...duuuh.which was obviously a
blocking operation and was blocking something in the background processes.
went 100/100 as soon as i took it out. thank you gentlemen.
On Mon, May 7, 2018 a
i will do that thanks MonteI must understand the cause of this before i
go into production ... otherwise I'll never sleep again :)
On Mon, May 7, 2018 at 9:45 PM, Monte Goulding via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Andre I think that should only be an issue if your numbe
Andre I think that should only be an issue if your number of requests * time
per request > client timeout.
Tom probably the best place to start is some logs of the requests and responses
on both client and server.
Cheers
Monte
> On 8 May 2018, at 11:28 am, Andre Garzia via use-livecode
> wr
Remember that LC is using a single thread and that script execution is
blocking, so, if your server is busy doing work to respond to a request,
then it will probably not acknowledge an incoming request at the same time.
Or at least that was true for my RevHTTPd version...
On Mon, May 7, 2018 at 12
Hi folks, so spent the last 2 days working on getting my client to talk to
a simple service I created taking advantage of the httpd library in v9.
Everything works fine. half the time. literally the request is
identical each time but the result differs.
the content type is set to text/pla
