|
If you've:
- stepped back, and gotten other people's feedback
on another possible solution; mainly to prevent a forest for the trees
perception of how to solve a problem
- confirmed moving it to the server would truly
take too much development time
- implemented something like this like you
mentioned you did:
- upped the scriptTimeoutLimit
Then all I can say is improve on the above by only
processing as many nodes as you can per frame on the lowest target platform
you're willing to support. In my multimedia days, we'd pick a target
platform CPU/RAM spec, test for that, and to hell with the rest.
The moniker of "web app" however apparently brings
the moral responsibility of "working well for the masses". App & Page
are 2 different things, but many people apparently can't tell the 2
apart.
...sorry for the rant; um, you could implement a
timer solution. Basically, instead of "processing 5 nodes per frame
because that apparently works well on most machines", you could instead
implement a timer that, if it takes longer than 8 to 10 seconds, it waits a
frame. The risk with this is if one node is particulary long it could
accidentally call the script timeout... BUT sometimes you may process just a few
more nodes than you usually would.
Another solution is to offload some things to
_javascript_. _javascript_, for example, has RegExp, and it's fast; Flash does
not yet. _javascript_ Pre-Flash 8.5 is faster a lot of times for some data
operations; see if _javascript_ can help too.
Good luck!
----- Original Message -----
From: Tracy Spratt
Sent: Tuesday, November 01, 2005 12:35 PM
Subject: RE: [flexcoders] script time warning and Flash Player
8 Yes, I really need
this. Jesse, if you are still
following this thread: Besides moving my entire process to the server(which
would take me several weeks, and this is a rare condition that only a developer
will see), is there anyway to “refactor” a single process? The is
the massive calculation (in this case it is building two 30,000 node trees) that
made me implement your status variable and doLater strategy in order to give the
user some visible feedback while this process is running. It is broken up
into individual function calls, but it still triggers the
time-out. From:
I do hope to refactor and optimize the code eventually,
but I think the option to override the default time limit of 60
seconds for your script should be made
available. - superabe
On 10/31/05, JesterXL <[EMAIL PROTECTED]>
wrote: I never knew it was an
issue. Incidentally, I think that is one of
the worst features Macromedia could of implemented in Flex, although, I
understand why they did it. My opinion; if you are using that
attribute of the application tag, it's time to refactor whatever part of your
code requires it. ----- Original Message -----
From: superabe
superabe Sent: Monday,
October 31, 2005 10:36 AM Subject:
[flexcoders] script time warning and Flash Player
8
Hello list, resending this, hoping somebody has an
answer. The scriptTimeOut property for the application tag does
not seem to be -- YAHOO! GROUPS
LINKS
-- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- Re: [flexcoders] script time warning and Flash Player 8 JesterXL
- RE: [flexcoders] script time warning and Flash Player... Matt Chotin
- [flexcoders] Big problems with SBC Yahoo Browser Robert Thompson
- Re: [flexcoders] Big problems with SBC Yahoo ... John Dowdell
- RE: [flexcoders] script time warning and Flash Player... Tracy Spratt

