Julija Alieckaja

hi @activeliang It's responsibility of a client code to prevent concurrent refresh requests. Basically, the JS client should disable page refreshing while there's a pending refresh request, and enable it...

@masterkain requests with the same access token can be sent concurrently, the gem does not add any limitations. Refresh token requests are supposed to be limited, throttling may lead to...

Hi @HLFH, Currently it doesn't support Mongoid. Yet it's possible to implement an adapter for it, you can see examples here https://github.com/tuwukee/jwt_sessions/tree/master/lib/jwt_sessions/store_adapters Feel free to open a PR with implementation...

Hey @plcosta, thank you! The gem doesn't have integration with devise, still those 2 gems can be used together by which I mean devise can be used f.e. for rails...

@plcosta sure, PRs are always welcome!

hi @j-manu, 1. Take a look at https://github.com/socketry/io-event/blob/main/lib/io/event/selector.rb 2. Fixed concurrency in the context of this gem is basically a number of jobs. It's possible to spin up any number...

2. Ah I see, interesting... I need to give it some more thoughts, but should be doable 3. Sure, I'll be glad 🙂

@blelump thanks for the head ups. As far as I understand each subscription is being run in its own thread but couldn't it receive multiple events which just get buffered...

@kozlovic thanks for your reply. > Do you know for sure that the server has processed and persisted the ACK for that message that you think should not have redelivered?...

Sure, here's the logs sample: On start (already receives outdated events) ``` events_1 | timestamp='2018-10-08 20:04:24 +0300' level=INFO message='NATS connected' events_1 | timestamp='2018-10-08 20:04:25 +0300' level=INFO message='[00e8c149-8d79-4e7a-9887-8c27970fac90] Received a message...