Conversation
|
@tommyo Sorry for the slow reply on this. I'm just trying to work through the backlog now. I'm at a point where I don't want to merge more store implementations into the main repository --- there are enough to maintain already and most of them I don't ever use (which makes running tests and maintaining them when problems arise awkward). Would you be happy instead to host this store implementation in your own GitHub repository? And then we can list it and link to it from the main README? |
|
@tommyo Did you ever create a repo for this? I was exploring Nats Jetstream for session storage and came across this PR. |
|
I didn't yet. I'll work on it this weekend.
…On Fri, May 30, 2025, 3:45 AM Andri Óskarsson ***@***.***> wrote:
*andrioid* left a comment (alexedwards/scs#212)
<#212 (comment)>
@tommyo <https://github.com/tommyo> Did you ever create a repo for this?
I was exploring Nats Jetstream for session storage and came across this PR.
—
Reply to this email directly, view it on GitHub
<#212 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAG5H6BZQTJMUDNNRNEGDD3BAD73AVCNFSM6AAAAABWSDXHIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRRGUYDIMZYGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Right now I don't think there is any further action to take, so I'm going to close down this PR. If you do create a repo, please let me know and I'll add a link to the README. |
This adds a nats jetstream KV store implementation as per #200