This set of commits implements timeline engine according to reference implementation @ pebble/pypkjs. It does not yet implement websync part, only core pin management - such as json parsing, serialisation, pin retention, reminders/notifications delivery, etc. I.e. interaction with the pebble.
As a side effect it fixes #35 and #37, prepares framework for #10 and #12.
It also removes (now obsolete) code which became unused.
LegacyNotification endpoint think also could be removed together with Notification class. But I leave it to you to decide.
Persistence is implemented as raw json files (with small header) - should be fine for a small scale but with websync probably would need sqlite as backing storage, to avoid keeping all pins in memory.
abranson
commented
8 years ago
This set of commits implements timeline engine according to reference implementation @ pebble/pypkjs. It does not yet implement websync part, only core pin management - such as json parsing, serialisation, pin retention, reminders/notifications delivery, etc. I.e. interaction with the pebble. As a side effect it fixes #35 and #37, prepares framework for #10 and #12. It also removes (now obsolete) code which became unused. LegacyNotification endpoint think also could be removed together with Notification class. But I leave it to you to decide. Persistence is implemented as raw json files (with small header) - should be fine for a small scale but with websync probably would need sqlite as backing storage, to avoid keeping all pins in memory.