rupl
commented
8 years ago I got a nice version of this working! There are two major problems I noticed while building:
- iPhone chrome doesn't send data when someone else logs in. Need to do some remote debugging to figure it out.
- Each peer sends the whole payload to the new user, who sorts through it and uses unique data only. I'm not sure how to avoid that duplication.
This is an alternative approach to using a DB to store the state of the app. I feel like it is something different to try as opposed to just storing it in a central store. Plus it emphasizes the co-creation we try to embrace.
When someone joins, the client should ask other connected users for their canvas state, and make a union of the responses to sync up with the others. The drawing will persist as long as one person is in the room, but the moment they leave, it's gone forever!