feat: Support https://github.com/AscendingCreations/AxumSession

[LeoniePhiline]

As the lockable axum-sessions is discontinued and tower-sessions is broken by design in concurrent contexts, support axum_session behind a feature flag, or even as default feature.

[maxcountryman]

tower-sessions is broken by design in concurrent contexts

This is no longer correct.

I would encourage you to reevaluate tower-sessions as it is now the most popular session crate in the tower ecosystem. Many folks are using it to good effect in large projects and it has replaced axum-sessions for all practical intents and purposes.

If you choose not to use it, that's perfectly fine by me but at the same time it is important to understand that it works well in (and in fact is designed for) concurrent contexts.

We'd love your feedback on the crate's discussion forum if you've encountered issues with the latest release and of course welcome contributions from folks in the community.

[LeoniePhiline]

@maxcountryman Thanks for your comment. I will be sure to re-evaluate tower-sessions.

I have recently started a new green-field project at work, and choosing a session manager is one of the next items on my list. I will upgrade axum-csrf-sync-pattern to axum 0.7 and make it compatible with the chosen session manager (or maybe with both, if time allows).