consent

First stab:

remove consent message type, send instance handshake instead and include consent state (I'm not fully convinced this is nicer than what we had, I'd be happy to revert this)
remove reconnection code.
only store and restore user action bits in storage.
minor code cleanups.
Do we have a test that lets us know that if a remote instance goes offline,
and then comes back online, the consent state is correctly restored?

On Wed Nov 05 2014 at 5:16:30 PM salomegeo <notifications@github.com> wrote:

> In src/generic_core/user.spec.ts:
>
> > -
> > -    it('sending message to offline instanceId prepares reconnection promise',
> > -        () => {
> > -      user['removeClient_']('fakeclient');
> > -      user['removeClient_']('fakeclient2');
> > -      expect(user.clientIdToStatusMap['fakeclient']).not.toBeDefined();
> > -      reconnectPromise = user.send('fakeinstance', msg).then((clientId) => {
> > -        expect(clientId).toEqual('newclient');
> > -        reconnected = true;
> > -      });
> > -      reconnect = user['reconnections_']['fakeinstance'];
> > -      expect(reconnect.promise).toBeDefined();
> > -      expect(reconnect.fulfill).toBeDefined();
> > -    });
> > -
> > -    it('delivers pending messages & fulfills with new client ID on reconnect',
>
> I deleted the reconnection code, we don't need it.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/uProxy/uproxy/pull/548/files#r19911012>.
>