message TTL not expire with inmemory storage provider

[cravler]

app.js

var client = require('emitter-io').connect({ host: '127.0.0.1', username: 'emitter-io' });

const key = '<key>';
const channel = 'demo';

if (process.argv.includes('--pub')) {

    client.publish({ key, channel, message: 'hello, emitter! ' + (new Date()).toISOString(), ttl: 10 });
    client.disconnect();

}

if (process.argv.includes('--sub')) {

    client.subscribe({ key, channel, last: 5 });
    client.on('message', msg => {
        console.log('>>> message: ', msg.channel, msg.asString());
    });

}

just run:

docker run -d --name emitter -p 8080:8080 -e EMITTER_LICENSE=<licence> emitter/server
node app.js --pub
# after 10 sec
node app.js --sub

[postacik]

I made a similar test with inmemory and ssd storage providers and confirm that last: n parameter ignores the ttl for inmemory provider. However it works as expected for ssd provider.

[kelindar]

Now that badger supports in-memory mode, I'm going to swap the existing in-memory implementation to badger. This will fix this issue.