Thanks for getting back on this one, Aparajita. All I can say is -
bummer. For a commercial web server, this seems like a pretty big
bug on
4D's part ... the whole "one request at a time" thing really isn't
very
cool.
we placed a
20 second WHILE loop directly into a page with no method wrappers at
all. Tried the loop with various combinations of "delay process" and
database queries to no avail.
Requests are received by the server,
queued, and are executed sequentially. In this case, shouldn't A4D
call
back to the scheduler after each iteration through the loop, thus
allowing another process to proceed?
Hmmm...that is not supposed to happen. I have verified that 4D is not
blocking in the second case. This leads me to believe the fault for
both cases lies with me.
I will look into it.
we need the information
returned from the method to display graphs on the page, so
asynchronous
processes won't work for us here.
I'll get this problem fixed on my end, then we'll see what happens
with calling 4D methods.
Regards,
Aparajita
www.aparajitaworld.com
"If you dare to fail, you are bound to succeed."
- Sri Chinmoy | www.srichinmoylibrary.com
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
