You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Marshalling and UnMarshalling should work reliably, and repeatability over multiple iterations of marshall & un-marshall.
Problem
When marshalling, the originActivity got lost, since we don't preserve full history.
It seems the overall approach of keeping track of the origin activity instance, from which the inbound state transfer was made,
is not well suited to keep track in e.g. MessageSubscription struct.
E.g. in the simple case when the origin was a StartEvent, we don't want to marshall that already completed instance information.
Hints
Having a gut feeling, that the commands should rather contain the origin activity information, and we might use some kind of command stack (similar like CPUs work when calling a sub-routine).
Also, the stack approach would help in nesting workflows as well.
The text was updated successfully, but these errors were encountered:
Goal
Marshalling and UnMarshalling should work reliably, and repeatability over multiple iterations of marshall & un-marshall.
Problem
When marshalling, the
originActivity
got lost, since we don't preserve full history.It seems the overall approach of keeping track of the origin activity instance, from which the inbound state transfer was made,
is not well suited to keep track in e.g. MessageSubscription struct.
E.g. in the simple case when the origin was a StartEvent, we don't want to marshall that already completed instance information.
Hints
Having a gut feeling, that the commands should rather contain the origin activity information, and we might use some kind of command stack (similar like CPUs work when calling a sub-routine).
Also, the stack approach would help in nesting workflows as well.
The text was updated successfully, but these errors were encountered: