Here's one situation: an A4D page which calls a rather long native 4D
method is executed (this method does not contain any plugin calls - in
fact, in one of my test cases, it was as simple as just looping for 20
seconds). This method takes ~20 seconds to execute, during which
time no
other connections to the server can be made.
Unfortunately this seems to be a problem with 4D. It appears that 4D
is not handling any web requests while the method is running. Once I
pass control to 4D to run the method, it is out of my hands.
I would post something on the iNUG. I will report this as a bug.
A second situation: same as above, except that the A4D page calls a
highly recursive A4L method. Other requests appear to hang until the
initial request has finished executing. Is the scheduler invoked on
code
within this library method, or only before and after the initial
method
call?
You are correct, this seems to avoid the bug. You don't have to
create an extra method in 4D, you can use the 'execute in 4d' command
in Active4D to call 'Execute on server' directly.
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/
