Can you answer this question?

[n0nuf]

Is there a reason when invited to a workplace containing a lot of data that the program seems to wait until it has sync'd all the data BEFORE actually opening the new workplace? Is there a way around this? When an invite is sent to have the program immediately accept and open the new workplace. THEN have the program begin the sync processl

Information appreciated.

Scott

[elnaffar]

Hi Scott,

If I am not mistaken, that is the exact behavior of Groove.

-Said.

[Franco Dal Molin]

Yes, currently this works as designed. After an invitation, the whole workspace is basically sent as "one initial single transfer" to new invitees. This has to do with maintaining consistency of the content.

Your idea of sending the empty "shell" first, and then gradually "filling it in" is good. We have discussed this approach many times internally and in development, but it introduces many new hard algorithmic problems. We might evolve towards it, but likely in small steps.

Possible intermediate steps could include providing better feedback about transfer progresses, basically "progress bars" per workplace and even on a per object basis.

On the other hand, the more we invest in boosting the P2P replication, e.g. by adding the capability of "fetching bits and pieces of content from any member peers that are online", the faster everything will work, and hopefuly the issue of "long waits" will be reduced automatically.