MM> Shouldn't we synchronize on whatever scope we invent that is the
MM> view-scope? Only one request may access the view (or its state,
MM> depending on how this is gonna change in implementation after we're
MM> through with 2.0) at a certain point of time, that's it.
AW> That's by far the simplest approach. This does cause major
AW> UI issues if you rely on it for AJAX requests, since one
AW> slow request (server/DB/network) blocks all subsequent requests.
IS> And now I think we should count separately Ajax vs regular requests.
AW> In terms of which? View scope, or state saving?
AW> If the former, I don't see why, if the latter,
AW> absolutely, in fact see:
AW> PPR + State Management: reuse state tokens while PPRing to avoid flushing
AW> It's a big win for state longevity (or for memory use,
AW> if you use it to crank down the size of the state cache).