geodan / cow.superpeer Goto Github PK

• Timestamps
• Websocket disconnect reasons
• Postgres disconnect reasons
• Start
• Parse errors?
• Startup analysis (amount of users, projects etc)

When the connection to postgres is interrupted, cow will die with:

events.js:72
throw er; // Unhandled 'error' event
^
Error: connection pointer is NULL

at Connection.<anonymous> (/var/data/sites/cow/node_modules/pg/lib/native/index.js:184:17)

COW should start polling the connection and retry.
After X retries cow should continue running but give a warning in the form of a status update in the peer object.

Put the configuration parameters into a seperate file, like cash is doing.

Projects are purged from the local indexeddb after x days. The superpeer (SP) keeps them forever (on a postgresdb) but there is no way to get them back from SP since SP doesn't keep them in memory.
There should be some special functionality in SP that can give a list of archived projects and possibly put them back in the sync process.