How to 'catch up' on changes made to DDS between container creation by one party and attachment by another?

[jonverrier]

Hi,

I am probably missing something.

Party 1:

1. Create container
2. Share URL with ID.
3. Start making changes that flow to DDS.
4. Party 2 attaches using the shared ID.
5. Party 1 makes more changes.
6. All changes made in 3 & 5 arrive together at Party 2 ( listening for DDS.on("valueChanged") ). But only when there is a new change made in step 5 following the attach by party 2.

I am listening for container.on("connected) in 1 & 4, still seem to be missing changes made in between the attach by party 2 and the next change.

The state is there as it arrives once another change is made ... in step 5. So having to store it all and replay after a manual handshake with new joiners seems unnecessary, and certainly complex with multiple parties.

Any help - how should I get the initial load of state that is already there when attaching to a container ?

Thanks in advance to anyone that can help.

Jon

[jonverrier]

Bumping my own discussion. My workaround is to write special 'null' objects when attaching, which seems to kickstart the data exchange process, and works for now. I ignore them in the main flow and clear them up later.

Will come back to this at some point to see if I can do a small reproduce.