flash actionscript: At times it may seem trivial, but it's a good idea in general because you
actually end up planning for the unintensional. While statistically you can
assume 90% of the time there won't be an issue with cpu speed, at what point do
you consider your cuttoff for robustness to be acceptable?

Example, can you assume that a user will be using only your app, without
anything else running in the background? (ie burning a dvd, DL'ing a file,
accessing a USB device, etc) whereby your app may or may not have access to
necessary cpu utilization that it needs.

Using event handlers does 2 things for you that I can think of just at the
moment, 1. it's much easier to read because it removes the dependency on
procedural code which is dependent on execution time 2. it helps to plan for
the unforseen glitches and allows you to build a better "state machine".

How important is it to use event handlers with local shared objects?

I'm creating an app that uses a large number of LSOs and the app will run as
a Flash projector. I've never had a problem accessing or writing from/ to a
LSO, but I'm wondering if users with slow CPUs will have issues. If I were
reading data from a text file, I'd use an event handler to check that all
the data have arrived before proceeding, but I'm not sure if this is
necessary with SOs.