(Obsolete page - consult Flows instead)

A "Multi-Request" is a sequence of POST operations (i.e. requests with the potential to modify persistent state) issued by the user that collaborate to construct a "unit of work" that should either be committed or rolled back as a unit. The most common idiom for requiring a Multi-Request is a "wizard", a sequence of related dialog boxes which the user is guided through in a linear fashion to build up a combined request. The user should at any time be able to "cancel" the wizard, leaving no change to the persistent state since the start, but should "see" themselves at intermediate times to be within a "transactional" state whereby their changes have actually been reflected.

RSF does not in essence define a separate type of scope to handle Multi-Requests, but instead chains together the state-altering potential of each individual request scope by amalgamating the individual alteration operations, which are tracked using tokens assigned to each view participating in the Multi-Request.

Like most things in RSF, the strategy for this should not be something that concerns the general user, but those who need a more thorough grasp of the conventions and mechanisms should refer to the pages on Multi-Request State Architecture, and on State in general.