Palindrom
Write spec for session handling/management
Could be considered a part of writing down all entire Palindrom protocol spec - https://github.com/Palindrom/Palindrom/issues/61
Given the ongoing process of writing NodeJS server-side to handle Palindrom communication, it would be beneficiary to have clearly defined behaviour related to connecting, creating the "session"/session resource, re-connecting, closing the connection, killing the "session, keeping it alive/heartbeat, etc.
Something is written at https://palindrom.github.io/docs/02-_Palindrom/ There are also few pages at https://github.com/Palindrom/Palindrom/wiki - probably outdated.
I started adding a few tests at https://github.com/Palindrom/Palindrom/blob/tomalec-wip-modules2/test/specs/client/heartbeat.js which is hard given the current operating implementation is buggy, closely tied to old Starcounter C# implementation, workarounds some SC-specific problems, and entangles logic which may be separated to a different layer.
Related issues: https://github.com/Palindrom/Palindrom/issues/91 https://github.com/Palindrom/Palindrom/issues/258 https://github.com/Palindrom/Palindrom/issues/268 https://github.com/Palindrom/Palindrom/issues/249 https://github.com/Palindrom/Palindrom/issues/240 https://github.com/Palindrom/Palindrom/issues/233 https://github.com/Palindrom/Palindrom/issues/173 https://github.com/Palindrom/Palindrom/issues/179 https://github.com/Palindrom/Palindrom/issues/240 https://github.com/Palindrom/Palindrom/issues/212 https://github.com/Palindrom/Palindrom/issues/208 https://github.com/Palindrom/Palindrom/issues/96 https://github.com/Palindrom/Palindrom/issues/201
@Starcounter-Jack feel invited to sketching it.
My take on that is uploaded at https://github.com/Palindrom/Palindrom/blob/c77f57ad7a53150c5f5a9effe0a3d225264cbb0b/docs/05-_Session.md and https://raw.githubusercontent.com/Palindrom/Palindrom/c77f57ad7a53150c5f5a9effe0a3d225264cbb0b/docs/img/Palindrom_Session.png