I've had the same "flashback" for a financial account site I inherited. Offshore work done in a hurry... In fairness, though, it's hard to constantly be on yo

I've had the same "flashback" for a financial account site I inherited. Offshore work done in a hurry... In fairness, though, it's hard to constantly be on your guard NOT to EVER update something that might be visible to another concurrent request. It's interesting that the MS web app model for .NET was to make a new instance of the service code for a page for each request, to at least avoid this problem the moment you "walked in the front door". TL;DR: shared.setState( "Oops!" );