Nikolas Poniros

Well I do need to write integration tests and more unit tests to make sure everything works correctly and reliably but it looks okay for now. But I can tell...

Yes I used the logic from the socket server example but the function call order is differently and this might cause the issues you are seeing. I use polling because...

@nevf just send me your code so I can get a feeling on how you are planing to use it before I implement something that might work completely different than...

@nevf thanks for the code. I will have a look ASAP. Yes you are right that `getNextClientID()` and also other methods interacting with `meta.json` should be async but sync is...

@nevf so I add a WebSocket server. It's not really tested yet but it might help you with your sync issues. I will try to test it later today. The...

@nevf make sure that you get a client id before sending changes and subscribing. The socket protocol in the dexie samples assumes a synchronous client id generation (this is needed...

Are you using the master branch? In master this would not work. In the socket server branch it should work. For master you will have to wait for the response...

@nevf so I found the mistake. I was using default params for `syncedRevision` and `baseRevision` but those don't work since during the initial sync Dexie.Syncable sends `null` and not `undefined`....

@nevf great to hear that. ~~I'm actually handling close in socket/server.js line 46 but I forgot to pass the connection id..~~ Fixed it now and found out that I can...

@nevf okay, thanks for the input