closes #28
Basic websocket implementation to track and broadcast basic user actions to showcase on home page.
Can't add INFLUENCE_BEATMAP_ADD or similar event because with current implementation, it's not easy to determine if we are adding map or adding a brand new influence (mongo upsert :fearful: ) I can do it in a way that's not efficient but I will come up with something.
also #31 SĞKSBKİSJİVAJİVAJŞFAJŞFAŞHFSŞJAFŞJ
Since we won't have it in documentation. I'm adding it here.
On first connection, server sends the last 10 activities to the client. After that, each client will get latest activity one by one as they happen.
There are 3 events. I will add one example for each:
closes #28 Basic websocket implementation to track and broadcast basic user actions to showcase on home page. Can't add
INFLUENCE_BEATMAP_ADD
or similar event because with current implementation, it's not easy to determine if we are adding map or adding a brand new influence (mongo upsert :fearful: ) I can do it in a way that's not efficient but I will come up with something.also #31 SĞKSBKİSJİVAJİVAJŞFAJŞFAŞHFSŞJAFŞJ
Since we won't have it in documentation. I'm adding it here.
On first connection, server sends the last 10 activities to the client. After that, each client will get latest activity one by one as they happen.
There are 3 events. I will add one example for each: