Why are nested conversations ( NC ) are also long running by default?, why I do not need to promote them? AFAIK if they were temporary Seam programming model would allow me to have a background LRC
and foreground
TCs. That way we could have a default
conversation pretty much equivalent to session scope as the parent of initial TC conversations. and that would enable code reuse between:
-
navigation cases
that work with long lived
components in the session and short lived
components in a TC and ...
-
navigation cases
that work with long lived
components in a LRC and short lived
components in a TC would be possible
What do you think about this? Don't you feel that there is something just not as consistent as it could be
in the way Session,TC, LRC and NC are handled now?
