Leszek Gawron wrote:
Do these different invalidation strategies make sense at all? If yes,
are others interested in seeing them in our code base? WDYT?
The best scenario in my case would be to keep not even a single
continuation tree but a single continuation chain. Any new top level
continu
ired.
If you implement a flow that uses some heavy-weight business objects and
you can't put them into global variables you soon run into problems if
this flow is executed many times by your users.
So I started to experiment with different continuation invalidation
strategies than the th
implement a flow that uses some heavy-weight business objects and you
can't put them into global variables you soon run into problems if this flow is
executed many times by your users.
So I started to experiment with different continuation invalidation strategies
than the the dfeault time-
