On 3 June 2015 at 15:10, Brian Wolff bawolff@gmail.com wrote: ...
I think this suggests that gwtoolset should have some sort of back-off feature when things start to fail (particularly due to "HTTP request timed out.") to slow down the request rate.
When I used to analyse big stuff like oil rigs, part of the basic 1980's engineering was to keep on poking at what happens during 'black out' and 'brown out' conditions. I guess in the post-Agile 2015 world this falls under boundary case testing. When we were specifying the GWT this was the sort of thinking for user friendly robustness that never made it into 'phase one'.
Charles' case is good stuff to tease out into some feature requests, even if we only park them for the moment. Hopefully with evolving strategies, the WMF will adopt more of this, or indeed provide a playpen where the nuts and bolts of internet transaction problems are handled by off-the-shelf secondary playpen modules. Okay, it's fantasy, but you never know. ;-)
Fae