currentTime not being updated in standalone... arggghh!

[Sivakatirswami]

skts wrote:
>> What happens: you can conceivably end up with 100's of
>>
>> updateTC  sitting in the pending message queue... this actually  
>> happened to me once and my application would slowly grind to a  
>> halt with users complaining they could no longer even type in a  
>> field... the CPU was so eaten up by processing the pending msgs  
>> queue.
>

On Apr 28, 2006, at 1:36 PM, Josh Mellicker wrote:

> Sivakatirswami, I WONDERED why typing in the notes field was so  
> slow!!! Thanks so much!!!
>
> I added the check back in and typing is normal and the counter  
> still works in the standalone.
>
> THANKS!!!


Ok then, probably you may not know this function (i didn't at  
first)... you have this diagnostic you can run in the msg box at any  
time you find your app is starting to get sluggish. Like so many  
things in Rev, simple, but if you don't know it.....

put the pendingMessages

It's will be obvious if you have a runaway queue... you will see  
100's of lines... but, unless you have some really long lead times on  
some messages that you are posting, (like sending messages 10 minutes  
later...or a hour later ) that queue should empty out rapidly or just  
have few unprocessed msgs... but if  the  number of lines just keeps  
growing and growing, you have a problem...


Wow I actually helped someone on this list after  all these years of  
just sitting at the feet of the xTalk masters

(smile)




>>
>>
>> if ",postTime," is not in the pendingMesssages then
>> 	send postTime to me in 1 second
>> end if
>>
>>