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

Add support for laminas/laminas-servicemanager:4.x #42

Open
alexmerlin opened this issue Jan 20, 2025 · 5 comments
Open

Add support for laminas/laminas-servicemanager:4.x #42

alexmerlin opened this issue Jan 20, 2025 · 5 comments
Assignees

Comments

@alexmerlin
Copy link
Member

Feature Request

Q A
New Feature yes

Summary

@arhimede
Copy link
Member

@arhimede
Copy link
Member

@arhimede
Copy link
Member

@alexmerlin why we are using laminas-session and not mezzio-session ?

mezzio-session does not use service-manager at all

https://github.com/mezzio/mezzio-session
https://github.com/mezzio/mezzio-session-ext

@alexmerlin
Copy link
Member Author

@arhimede dot-session was built on top of laminas-session since the beginning of the package, because at that time (dot-session since 2016) only laminas-session existed (2012 vs mezzio-session since 2017).

Switching to mezzio-session (with its storage extension mezzip-sessio-ext) is possible, but in order to avoid using both laminas-session and mezzio-session in our projects, we should also modify our laminas-session-based dot-* packages: laminas-session dependents.

Also, there are Laminas packages using laminas-session (like laminas-authentication, laminas-form etc) so, even if we remove it from our packages, Laminas would still use it in parallel with mezzio-session.

@arhimede
Copy link
Member

Maybe laminas-session is too complex for our needs ?
we need middleware implementation, and not MVC too

It is a good moment to have this discussion and decide now between those 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants