I have the following use case:
A user can modify a number of pages concurrently, and then commit the all the modifications together. It makes sense to me to model this as a master conversation (that will do the committing) and a nested conversation for each page.
Is it possible / safe in the master conversation to then call a 'save' operation on a component in each nested conversation?
I cant see an obvious way to access components of different conversation contexts, short of creating a new ServerConversationContext for each nested conversation. Also - will SMPC get angry if I start messing round with a conversations that has not been initialised as part of the normal lifecycle?
I get the impression that I should really be working with 'one conversation per request'?