Still working on the syncing, or more specifically its ramifications. This turns out to be a process that is much more involved than we originally thought, but it's an excellent test case to challenge many assumptions that we've made before.
The end result will be a much more solid core, but it will take more time than originally thought :-) Some concrete examples: * we still need to make sure that the anonymous learning data gets submitted to the server only once. No problem if there is only one Mnemosyne client per user, but if you have many more devices (mobile phones, desktop, ..) in the mix, then this becomes something to think about * originally, we sent across each event in the syncing process on a separate line. This is very easy to code, but breaks when there are newlines in the card's data. The best solution is not to rely on linebreaks as separators. This requires some extra coding to make sure we don't use too much memory, but on the other hand it will allow us to send the data across in much larger chunks and improve throughput. I could think of many more examples, but you get the idea of the kind of stuff I'm working on now. Cheers, Peter -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en.
