Hi Martin,
Can you give some details about conversation?
A.C.
Martin Kersten-2 wrote:
>
>
> If not, stick to conversation (use an Id). Such a general
> conversation service with saving the conversation to db in
> a distributed system is almost every time the right thing
> to go to implement
If the user is restricted to see the same data once use
ASO or @Persist. It is no harm if you have a user fiddling
with such a form and seeing the same data twice.
In filling out a lengthly multipage questionary about
registration I would think of harmful behaviour using the
same formular twice
