On 21 Sep 2010, at 22:42, Aparajita Fishman wrote:
That is just plain bizarre.
If you don't think that squares with anything then it may be that the
process number is being reported falsely somewhere in my debug code or
by 4D.
This was just a quick preliminary finding because, although I broke
the rules by passing component variables to a plugin, that method
shouldn't have been executing at all and I decided to find out whether
it was in fact.
I made the component method (the one calling A4D GET SESSION STATS)
write to a text document every time it ran and record the time and
'Current Process'.
The result was that the log contains entries as follows:
[1] - between 10 and 15 consecutive calls to the component method
every 10 seconds (i.e. there are 10-15 calls in the same second, then
a delay of exactly 10 seconds, then another 10-15 calls and so on)
[2] - the process number logged (by the component method) was process
6, which on cross-checking with runtime explorer was the
A4D_Housekeeper process
Needless to say, the source code of the A4D_Housekeeper method does
not call that component method. It does, however, (in my
implementation) call another component function which returns the
state of the application 'quitting' flag.
************* Looping block in A4D_Housekeeper method (runs in host)
*********
While (Not($APP_QUITTING))
A4D HOUSEKEEPER
DELAY PROCESS(Current process;100)
$APP_QUITTING:=app_is_quitting <-- this is a component function
(not the same component as the session stats one. It just returns the
state of a boolean variable)
End while
I'll do some more investigation and see if I can determine if there is
something else at work causing problems.
Regards
Peter
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
