You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tracking issue for anyone interested in my attempt to implement NEW_TOKEN utilization. Thanks so much to Ralith and djc for the effort spent workshopping this with me so far!
7. Utilize NEW_TOKEN frames #1912 (depends on 5.) (note: implementation of BloomTokenLog and InMemTokenStore can be removed from 1912 and shunted to follow-up PRs)
8. PR to implement BloomTokenLog as default token log (depends on 7.)
9. PR to implement InMemTokenStore as default token store (depends on 7, thus can be created simultaneously to 8.)
Possible future followup work:
Allow more manual usage of tokens on client side
Allow more manual usage of tokens on server side
Allow encrypted application data to be placed in token
The text was updated successfully, but these errors were encountered:
Tracking issue for anyone interested in my attempt to implement NEW_TOKEN utilization. Thanks so much to Ralith and djc for the effort spent workshopping this with me so far!
Already done:
Anticipated future dependency path:
IncomingToken
#2094SocketAddr
by value #2107 (depends on 2.)ConnectionId
by value internally #2109 (depends on 2.)BloomTokenLog
andInMemTokenStore
can be removed from 1912 and shunted to follow-up PRs)BloomTokenLog
as default token log (depends on 7.)InMemTokenStore
as default token store (depends on 7, thus can be created simultaneously to 8.)Possible future followup work:
The text was updated successfully, but these errors were encountered: