Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Persistence mechanism for QoS 1 and 2 incoming and outgoing messages #3

Open
alsm opened this issue Mar 20, 2014 · 5 comments
Open

Comments

@alsm
Copy link
Owner

alsm commented Mar 20, 2014

No description provided.

@alsm
Copy link
Owner Author

alsm commented Mar 20, 2014

To properly support QoS 1 and 2 the messages should be persisted during the handshakes. It's common to offer a memory persistence instance that is ephermeral but suffices while the server is running, and another more persistence instance. For the latter I'm thinking of using Redis.

@mcollina
Copy link

I suggest you to try LevelDB. I used it for http://npm.im/mosca and it's awesome!

@alsm
Copy link
Owner Author

alsm commented Mar 27, 2014

I haven't tried leveldb before, I'll give it a look thanks.

@tennessine
Copy link

hello, mcollina

@mcollina
Copy link

hello @w3hacker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants