Little too complicated for me. I just shoot at problems with a shotgun and then check to see if I hit anything.
Bob On Aug 3, 2010, at 6:47 AM, Andre Garzia wrote: > Folks, > > I never seen a RevServer bug like those timeouts and stuff and of course > Jerry is not making it up, so the logical conclusion is that there's some > specific case(s) where a RevServer script can go loco and fail. > > After that conclusion, our first requirement is to draw a mental map of what > is involved. Now repeat after me SETUP > > S - Scenario (what are they building) > E - Environment (what is the surrounding environment) > T - Technology (what are they using) > U - Usage Case (what happened/when happened) > P - Possible Points of Failure (critical things that need assessment) _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
