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

Support persistent storage for inbound and outbound message sequence numbers #2

Open
kpavlov opened this issue Feb 19, 2014 · 2 comments

Comments

@kpavlov
Copy link
Owner

kpavlov commented Feb 19, 2014

It should be possible to persist inbound and outbound message sequence numbers for restoring session after disconnect. Add settings similar to QuickFix ResetOnLogon, ResetOnLogout, ResetOnDisconnect, RefreshOnLogon (see http://www.quickfixengine.org/quickfix/doc/html/configuration.html#Session).
Use persisted settings if FixSessionSettingsProvider.resetMsgSeqNum() == false.

@guidomedina
Copy link

About that, I'm planning to convert SessionRepository to a sort of an interface so that I can provide my own SessionRepository, the idea is to get the sessions from a distributed map say, using Riak or Redis or Hazelcast or any KV distributed solution (GRID like)

@kpavlov
Copy link
Owner Author

kpavlov commented Feb 15, 2015

SessionRepository interface was introduced

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

2 participants